Posted by Grant Foraker on January 07, 2008 at 13:31:34: Uploaded files: 2
Set up a new VB project for customer "PAC". Pasted in an IDD from another customer and built the INC and DLL. Added them both to Comet on the PAC directory. Copied them both to the CH1 directory.
Copied in BEL.IBS from another customer to the CH1 directory, made changes, and have a clean compile. I get the "Unable to load DLL" message from COSWIN. I've added my own message that shows the DLL and DIR being requested.
I tried setting the DIR sequence in my INI so that CH1 came ahead of PAC and also moved the source, DLL, INC and OBJ back to PAC. That seemed to work. Feeling brave, I copied everything back to CH1 and it started to error again. I deleted everything from CH1 and now it won't work from PAC either. See screen shot of message and CometEx.
The Debugger shows the DLL being found (FILEFIND) and goes wrong in a DOSRW just before the end of CW.CreateAutoModeDialog. See screen shot #2.