Since you cannot debug the program by running it in the VB IDE, perhaps you could add the ability to write to a log file, and in the area where the problem is occurring, log everything the program does.

That way, you can go back to the code and at least figure out the line that is raising the error.

Once you’ve done that, yo can remove most of the logging that you had put in, and add intensive information gathering right around that statement, to get a better idea on any environmental/contextual issues that might be causing trouble.

Or at least you would be able to post here the problematic area of code.

Hi Gonzalo,
Sorry about the long delay in replying; I had to take a couple of days out.
I program is using VisData (from VB6)but I am now trying to solve by writing a second Database in M/S Access. If this has no effect I shall rewrite the program frame by frame and try to isolate the fault that way.Very many thanks for taking an interest in my tales of woe, it is very much appreciated.

My thanks also to Woodie and Brain Wren, the replies gave me lots different ideas to work on.
UKBrad

A R Bradley

It shouldln't be too hard to search the registry on a machine where the applicaton DOES work for the class id that is being displayed. Using the information you get that way will tell you a great deal about what needs to be fixed.


Woody Z
http://www.learntoprogramnow.com
How to use a forum to help solve problems
My blog... please visit