11/29/2024 6:22:25 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss SalesLogix synchronization and remote database management. View the code of conduct for posting guidelines.
|
|
|
|
Remote Office Database Creation Problem
Posted: 12 Sep 07 5:02 PM
|
Ok, I have set up a remote office database several times, especially with my current configuration (which is SLX 7.0.1 with SQL Server 2005), and I can't get through this current issue which showed up for the first time. The database creation process gets almost all the way through, and on the "Create View" process, it errors out with the following message:
Step: stpExecSQL_CreateViews returned error: Line 6: Incorrect syntax near 'OPPORTUNITY'.
I looked through all the views to check syntax, and I even opened all the views to see if any gave me an error, and they don't. I even tried running some of them on a SQL Server 2000 server (that I use to create the database), and they work just fine on that.
Has anyone seen this before, or does anyone have any idea what this might be? If not, any idea how I can figure this out? I tried using the profiler last time, and it didn't give me very much information.
Thanks! |
|
|
|
Re: Remote Office Database Creation Problem
Posted: 12 Sep 07 5:23 PM
|
I have ran into this issue in the past.
Someone had created a view using constructs that only work on 2K5, and off course, the Remote DB wouldn't cut since it is executing on an SQL 2K server.
So, what to do:
- Identify all the views that you have that reference the OPPORTUNITY table
- Run each one of them on your SQL 2K to see which one doesn't work. [This doens't mean via Query Analyzer, but rather against a Copy of the DB that is loaded running on SQL 2K]
|
|
|
|
Re: Remote Office Database Creation Problem
Posted: 13 Sep 07 4:09 PM
|
Woohoo! I finally created a remote office database. It seems this is such a struggle every time. I took your advice, and I build a tool to run SQL Statements on another remote database with SS 2000 through the provider. After going through a bunch of views, I found four that were iffy - two that had commented sections (and those sections weren't near the word Opportunity) that didn't run in the tool I created, and two more that did run in the tool I created, but they employed the use of quotation marks around the aliases (and next to the word Opportunity). After altering all four of those views, I then ran into another, more familiar problem I kept having with some other views. I removed those views, and now I have a remote database!
Thanks for your assistance and thoughts, Raul. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|