4/25/2024 2:32:47 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 SQL Server or Oracle database administration related to SalesLogix databases. View the code of conduct for posting guidelines.
|
|
|
|
Remote Office Missing Sage User-Defined Data Types
Posted: 06 May 09 10:57 AM
|
We just noticed that our four remote office databases do not have any of the User-Defined Data Types that are in the host database - STANDARDID, TEXTBLOB, PICKLISTID, etc. Our SalesLogix version is 7.5.1, and the database version is SQL Server 2005.
Is this normal and expected that remote databases won't have the User-Defined Data Types? Should we be worried about this?
We are seeing a ton of failed transactions from the remote offices, and they are ParamSQL transactions involving fields with the User-Defined Data Types. The specific error message is "ParamSQLUpd - Error applying ParamSQL transaction A23TQDG : List index out of bounds (0)." Not sure if these errors are at all related to the missing User-Defined Data Types, but our inquiry into Sage is taking forever as usual, and our databases are falling out of sync.
Thanks! |
|
|
|
Re: Remote Office Missing Sage User-Defined Data Types
Posted: 06 May 09 7:36 PM
|
As far as I know, these User-Defined Types are not used by SLX. They may be there from previous versions, since upgrades won't remove them.
Never the less, they are just aliases for actual Field definitions.
Regarding your error messages, I would suggest that you use the TranViewer to analyze the statements. By doing so, reather than just getting the Error message, you would be able to get the statement that failed, and then figure out the cause of the problem. |
|
|
|
Re: Remote Office Missing Sage User-Defined Data Types
Posted: 06 May 09 10:23 PM
|
Thanks for replying! I appreciate you taking the time to help me out.
The reason I was thinking that the UDDTs might have something to do with it is for the same reason a normal SQL statement would give an error - if you try to reference an alias, and you never assigned one to the table in the first place, it'll throw an error. Either way, it appears the 7.5.1 eval database still has the types as well. Does we know for sure if these types are necessary anymore? We're just now setting up the remote office instances of our QA environment, and we may be able to test out different things to resolve this at that point. As I haven't heard about any widespread panic across SalesLogix 7.5 remote database customers, I suppose it may very well be just us... 
As for the error messages during synchronization, I actually looked at them using the Transaction viewer. Our BP plans on watching the profiler while the sync client is applying changes to see if that offers any more insight. |
|
|
|
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!
|
|
|
|
|
|
|
|