Beginning VB 6For coders who are new to Visual Basic, working in VB version 6 (not .NET).
Welcome to the p2p.wrox.com Forums.
You are currently viewing the Beginning VB 6 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developersí questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
1. Try the Dr. Watson log (Dr. Watson Errors are windows system errors and thats what this looks like).
2. Try the System & Application Event logs.
It is also possible that no error log is really created despite Windows saying there is one. How good is the error handling in your application? Try to shore it up. You might be able to trap the error (though possibly as I said above it is a Windows System Error and those are not always trappable).
Usually the way to find what the trouble is is to add a routine that writes to a file of your choosing, and put copious entries into that file denoting what is going on. entries when entering functions, entries when leaving them, actual strings that will be used to open recordsets or files, etc., including the time with each entry.
When the error occurs, go to that file to find out where you were just prior to the error.
I am a big fan of using the Windows Scripting Host, the FileSytemObject within it, the TextStream object of the FileSystemObject, and the WriteLine method of the TextStream Object.