>>I am attempting to register some 16-bit functions in my application, using RegFn() in the FOXTOOLS.FLL library. The functions I'm trying to register are for an external toolkit from ZyLab for full-text indexing.
>>
>>At first, the RegFn() attempt was failing universally. I got it to work by temporarily changing the FoxPro default directory to the directory where all the ZyLab .DLL files are. When I did this, the functions registered successfully (and were called successfully, as well).
>>
>>But when I complile my program and run it as an .EXE, it fails. When it gets to my line of code witht the RegFn() call, it pops up a File Open dialogue. If I cancel from the dialogue, I get a "File does not exist" error. If I select a file in the dialogue, I get an error that reads "DDEInit failed". But, as I said, if I run my source code inside FoxPro, rather than as a compiled .EXE, the functions register and execute with no problems.
>>
>>Any ideas?
>
>Mark,
>
>It sounds like FoxPro cannot "see" the DLL at runtime. You might try making sure that the DLL is on the DOS path, in either the Windows or Windows\System directories, or supplying the fully qualified filename.

George,

Thanks for the attempt, but I've tried all of the above. I've tried putting the DLL files in the program directory (where my application runs), the windows system directory, I've fooled with the DOS path. The application finds them just fine when running from source code inside of VFP. But the compiled executable is not finding them, or some other problem is occuring.

The "DDEInit failed" message is interesting, because nothing I'm doing involves any DDE communication that I'm aware of. Does this have something to do with the way FOXTOOLS registers 16-bit functions?

In any case, the problem is now moot (for me) as I was able to get the 32-bit toolkit to work (it wasn't before), so I no longer have to worry about registering the 16-bit functions. I'd still be interested if anyone understands what was going on with this, though.

Thanks,

Mark