Hi All,

There is a computer (Windows 7 64-bit) running my application, and causes the OS to ding whenever a user attempts to load the application. Other computes including my own are fine, even on a clean machine, which I have tested. It seems to me one or more items are either not present, did not load, or whatever on the user’s system.

I created a copy of the application and included all references but none of the source files except for a module containing Main() and inside that a MsgBox call so that I know that the app loaded. That worked. If I include all the source files but the Main() entry point just has the single MsgBox call and nothing else, does not load forms or anything else, the OS dings meaning that it could not find one or more references. The stripped out version without the source files that worked included all component references.

Correct me if I am wrong, but it seems to me that VB6 when it builds the executable only includes a reference into the executable of a Projects | Reference or a Projects | Components if the component is used somewhere, otherwise it does not include the executable reference, even though the project file mentions it. Am I right?

That leads to my question of how do I relatively easily determine which executable reference (VB6’s reference or component) caused the failure upon executable load? One thought that I had is to create what feels like a zillion test applets, one for each reference (VB6 reference or form component) used, but I could still miss something, even if I go through that humongous work, because the OS might be thinking of something that I am not. More so, I am positive that there has to be an easier way to find out which reference causes the build on the user’s machine. I tried VBWatch, a tool that I have to instrument debugging code into the app, but that only takes effect after the executable loads and runs, not before it.

Thanks in advance,

Sarah