Printable View
I have recently changed from a peer to peer configuration (using XP) to a SBS Server 2003 machine with the same connected workstations.
The peer to peer connection never gave any problems.
We are now experiencing the 3043 error intermittently (which pops up and the program then crashes)
My central database is Access 2000 and I am using VB6 as the application programming tools. Database access is predominantly ADO with some DAO
Has anyone any insight into this problem ?
Don't you have the source for the application? My advice is for you to put an error handler to all procedures where an error can be expected, I think MZTools can do this for you automatically. As such you can get to the bottom of the error and dig from there.
This has already been done
I always build in error handlers which not only pick up the error but also show me the exact place the error happened
Eg,
Code:Just before a file or database command I'll put in something like
ECode = 32 'position in the program
On Error goto EHandler
.... Commands
ECode = 33 'position in the program
On Error goto EHandler
... Commands
..
Ehandler:
Msgbox Ecode .... etc
The problem is the program just crashes without logic - this suggests its the operating system causing the crash which as we know, is difficult to debug
That would be strange. Have you peek at Events Viewer if you can find something about the crash?