Some of my VB apps used to do that. One issue was the ODBC driver I used and another case was I was creating more arrays/objects and never was deleting them. For me, it was not a Windows 2000 error. In these cases, the fixes were to update the ODBC error and correct my code.
We occasionally get this error in our application. Its a VB app, running all the time on a Win2K box.
I checked but didn't find anything in the system/application log
Any clues why this is happening? I am also chasing a 'memory-leak' problem in the same project. After having run for 15-20 hours, the EXE shows up to 80-90 MB of memory usage in task-manager and increases more than that on occasions.
I am wondering if this error is related to any memory problems my application has