ashumway

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.

We're running Glovia on Windows 2000 and our users have a tendency to close out their sessions when they get record locks. We've tried training them to not do it, but someone seems to close their session at least once a month. How do I prevent users from closing the ProIV client - either by cllicking on the "X" on the upper right corner of the window, or by using the menu? I've already taken away their ability to startup the Windows Task Manager.

We're running Glovia on Windows 2000 and I want to force uses to log into Glovia as the operator they're logged into the PC their starting Glovia on. How do I pass the OS Username into the Glovia startup and start Glovia automatically? I don't want to let the users change their username in the startup window.