Posted by Grant Foraker on May 26, 2006 at 08:02:33: Uploaded files: 1
At the LV meeting, I asked about making my DLL files visible to Comet. Mostly as a memory aid to make sure I deliver the updated DLL's along with the updated OBJ's. Brian suggested I add them as TXT files. On my development laptop I gave it a try. Everything worked.
Yesterday, using DOSCOPY, I transferred one OBJ and one DLL to a test directory (DAV) on my office server that also serves as my XAP and CAW server. I tested the the new OBJ using CAW from within my office and remotely from the Internet. OK so far. Next, I copied (Q#4) the OBJ and the DLL to the production directory (FST).
The OBJ would fail with an "Unable to load" message from CosWin. I added a message box to give me some of the details.
-------------------------------------------------------------------
cosDllNames$ = "DAVWIN.DLL" ! DLL filename
cosDllDir$ = sub(pstat(PARTITION$),41,3) ! Same dir as this program
cosDlgId = IDD.ZE ! Dialog ID
!===== If your dialog was designated as "child" it will be modeless. If "popup" it will be modal.=========!
!
gosub CW.CreateAutoModeDialog
If cosDlgOpen = FALSE
LET MBMSG$ = 'DLL=' + cosDllNames$ + '@0D0A@' + 'DIR=' + Dir$
LET MBMSG$ = MBMSG$ + '@0D0A@' + 'PATH=' + cosFileNames$
MSGBOX(MBMSG$)
!!!!! print "Dialog execution failed"
go ProgExit
endif
--------------------------------------------------------------------
See the attached screen shot showing the message box, DIRCAT, and Windows Explorer. davwin.dll is right where it's supposed to be but COSWIN can't find it.
Worked on this all yesterday afternoon and part of last night. No luck. During my testing I found a way to get even the "good" version on DAV to fail. One try was to use Q#13 to remove the QDIR entry for the DLL on FST but that didn't work either.
This morning I decided to finally upgrade the production server to 2006. It had been running 2005.369 just fine.
1. Upgraded to 2005.371. No fix.
2. Upgraded to latest Comet Serve and 2006.372. The DAV version began working again but the FST version still failed.
Everytime I changed the OBJ on my development PC I'd had used DOSCOPY to transfer the OBJ and DLL to DAV and used Q#4 to copy them to FST. Heck, that's why I wanted the DLL visible to Comet. Like the proverbial "last place I looked", it occured to me that I should return to my old delivery method and use DOSCOPY to deliver the OBJ and DLL to FST.
On the production server, I DOSCOPY'd off of DAV (now working again) and back onto FST. Voila!!!! Now I can get it to fail!!!
Wish List for Brian: could you make the CosWin "Unable to load" message include the DLL and DIR names.