Mark,

If you use that dequote project as a starting point, it's really easy to add C/C++ functions. The project is an old VS6 one, but the other night VS2005 opened it up with a conversion dialog and I only had to tweak a couple of linker options it was throwing warnings on. To add a function you only need update the .h for its declaration, the .def file to export the entry point and add the new member function to the class. I've just always found the LCK route too much of a headache with all the hoops you have to jump through to create FLLs. If you don't need to make callbacks into VFP then DLLs are just a lot cleaner.

>It's frustrating having written, in my time, hundreds of thousands of lines of C/C++ code and assembly language on non-Windows platforms, and then be faced with the "become good with it in Windows" learning curve. Learning the details of how to use the linkages between the VFP API and a DLL/FLL, all that encapsulated MFC stuff if that's the direction one wants to take, and even learning how to use VS to compile a C source that includes (when necessary) all those arcane Windows include files, etc... I am indeed still a neophyte there. Even more a neophyte with .NET. I wish I had a (revenue generating) project that would immerse me in such activities.
>
>Thanks again. What a fabulous resource is UT.