4/29/2024 12:30:26 PM
|
| |
| 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 using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.
|
|
|
|
Multiple-step operation generated errors. Check each status value.
Posted: 05 May 06 11:09 AM
|
augmentin generico augmentin generico prezzo fiogf49gjkf0d Getting this error popping up time to time on a screen in slx, also getting this error using scribe to populate the same table in the database occasionally, but once it happens to a record, it consistently happens(in scribe). If I write sql and pass it to the provider, it works great. Any ideas on how to trace this fully? I'd put some more tracing in the form (didn't originally develop it), but I'd rather trace it at the provider level, because I can make it happen any time using Scribe. The values don't seem to be out of the ordinary, and it's only updating two fields in a table for a record.
Any ideas?
Thanks,
Steve. |
|
|
|
Re: Multiple-step operation generated errors. Check each status value.
Posted: 05 May 06 3:00 PM
|
fiogf49gjkf0d turns out that we may have figured it out... I think it has something to do with dates and the switch to Daylight Savings time. Any record that is trying to be updated that has a date between 1:00 am Apr 2/2006 and 7:00 am on Apr2/2006 will generate the error. If I go to the db and modify the modifydate to something outside of that range, the update will work great. Now, to figure out how to push these changes out  |
|
|
| |
|
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!
|
|
|
|
|
|
|
|