We've got a batch job that runs every minute or so, to transfer data from a non-Pro IV Oracle DB to Glovia. This batch job runs some Pro IV code that checks some Pro-ISAM files and then does a SQL call to use a stored procedure to move the data from one DB to the other. About once per day, we get a Dr.Watson error (access violation). I checked with Microsoft and they say it's caused by Pro IV.
I've tried using exception handlers in the stored procedure, but haven't gotten any result there, so it doesn't appear to be caused by the SQL code. Does anyone have a ideas about how I could track this down in Pro IV? The error doesn't happen every day and I can't force it to happen.
We're running Pro IV version 4.6 on Windows 2000.
ashumway
Member Since 05 Nov 2003Offline Last Active Jan 27 2005 06:52 PM