I would like not to spend my weekend figuring this out so I am hoping someone knows the answer or absent that, has a couple of good theories. We are talking about Xalan/Xerces C++.
I am running some Xalan/Xerces stuff under Borlands Delphi 5.0. Its pretty trivial. I do a loadlibrary on a dll and then getprocaddr and then make the function calls as needed. I have done this a million times and have other DLL's in the same .exe that are working fine using this technique. Here is the wierdness. I have a DLL that is roughly modeled after the sample STreamTransform sample in Xalan. When I attempt to loadlibrary on this dll the call fails with no errors and the Getlasterror code of C0000090 (no clue what that is). Anyway, what I did was resort to dumping the dll using a borland utility tdump, that shows imports/exports/ dll's and other stuff. I then attempted a loadlibrary on each imported lib in my dll. I can load the xercesxxx.dll just fine, I can load the xalandom just fine, but when I try and load PlatformSupport.dll I get the wierd behavior. LoadLibrary returns 0, without any other windows messages popping up (usually if you are loading a dll via loadlib and it also loads other dll's that are not accessible in the path, then you get a popup dialog telling you which 'sub' dll's were not found.) I can run this down the hard way by debugging PlatformSupport.dll, but was hoping someone else might have a clue, as clearly I do not. I do have blonde hair! thx fhc Fred Covely BCF Technology [EMAIL PROTECTED] (B)760-631-8157 (C)760-717-9689
