Hi Ashtud,
You're not complaining about foxpro, you're complaining about an old version of it. That's okay.
You can be proud to do things with FP 2.x it was not supposed to do. Well, in fact you only programmed some stuff you'd be able to do in VFP anyway. '*' as Password char? It's in VFP as long as I remember.
You're (and your boss) are really wasting your time and money, it's dumb. Updating to VFP is much cheaper than to program certain features in C, viewing it from the aspect of what more features VFP offers. As if you could program everything VFP now offers for about 600 bucks...
It's more than just a recompile needed, but in fact it could work for a start, as VFP is very backward compatible. New features and functions were incorparated without killing older ones. The disadvantage is, you need to redesign to take advantage of new ways, but you can do that by starting from where you are.
Well, your boss seems so narrow that you'll need to do such low level stuff yourself, but maybe you're also stuck in your C world.
Maybe there is even SYS(2600) in FP 2.6, which besides some Memory API calls is a way to adress the RAM directly. But getting at the memory adress of a variable is something you only need in C, not in VFP. Think of the errors you surely made with pointers pointing to wrong adresses. In VFP you're quite safe to not do these errors. Even for API calls you know you can simply stick together everything in a string. BINTOC() is a function capable to do most of the needed transformations of int, float etc., it was much improved in VFP9 with the capability to convert with any needed byte order etc.
And if you intend on working on VFP variables from C code you do that by writing an FLL with the Library Construction Kit. Bit it may have been introduced in FP3 only. You can also do that with VS 2008 C++, and you can work on variables and tables from C that way.
But you need few API calls within VFP anyway. Creating a GUID, that's one thing. Shellexecute (well, there is RUN /N, but Shellexecute often is more capable).
You might like this FLL to help you as a bridge to the C world:
Don't know if this will work from FP2.x though.
Bye, Olaf.