<< I do this frequently. Have the compiler output to the RBase directory or actually use DLLoad. If you use DLLoad you can specify the full pathname to the DLL, so it can be in an "otherworldly" location out of the normal searchpath. >>
I actually _was_ using the DLL output from the Delphi compiler, although I've since changed to copying the DLL to a separate directory. The directory containing the DLL is the current working directory when I issue STDCALL and DLFREE, and I'm not including path information in either call (although I _did_ try DLFREE with a full path to the DLL file and both with and without the exetension specified). I couldn't get it working in either fashion. In practice, I will probably want to use the Windows loading facility to find the DLL without specifically stating where it is. << BTW, are you using the ChkFunc to conditionally call STDCALL so you don't call it repeatedly in the same session? >> At present, no, I'm responsible for manually calling the setup routine once per R:Base session. In my "release" version of the setup code, yes. -- Larry
