>>
>>No go, Craig. You can't #define function names, AFAIK. I've tried your example, and tried
>>
>> #define myfunc(a,b) abs(a+b)
>> ?myfunc(1,2)
>>
>>But it displays several very imaginative error messages, depending on the way you try to fool it - and still doesn't go. Clipper had something like this, and though it would make for more unreadable code and a more complicated compiler, I'd still like to have it.
>>
>>You can still
>>
>>#define ConfigFile sys(2019)
>>#define PushText Fwrite(fHandle,
>>
>>and then do
>>
>>modi comm ConfigFile
>>fHandle=fcreate("whatever.txt")
>>PushText "Hello, world")
>>
>>...and greatly reduce the typing efforts and readability :)
>
>
>Hmm...ok...it was just a thought. I'll pass on the original request to Microsoft.

Hi,

After reading this thread, I would like to see VFP 7.0 to be on par with the rest of VS product. Comprehensive support for all ActiveX variation (like containership ActiveX). Real Windows Control (buttons, toolbars, checkbox ,etc) and GUI interface. This is important if you want to use automated QA programs. User replaceable FOX errormessages. Ability to build VFP application into ActiveX component not just COM/DCOM component. It is a shame that a good development tool and language is left behind with such glaring deficiencies. Thanks.

Regards,
Kueh.