Cristof,

>>In the past I used C/C++ to write FLL libraries to write VFP functions which requires structures with pointers to API calls. For example:
>>
>>- Handling and querying printer properties
>>- Maintaining user accounts on a NT domain.
>>- Seeing who has a particular file in use.
>>- disconnecting people from the application and such.
>
>I tend to disagree with you here. *s* All this can be done in pure VFP, the latest version of my struct class for example doesn't use a FLL at all to implement structures and pointers. Sure, a FLL executes faster and if you start from the scratch in VFP, it's easier to write a FLL (if you know C, of course). But with a class like my struct class (or the pointer class or ClsHeap and all the stuff othere here have contributed) there's not that much you can't technically do in VFP (or VB, if that matters) and which matters for a business application.

I know. i'm aware of your truly great contribution on this one. That why I wrote 'in the past'. Sadly i haven't used your solution yet, i've only some limited experiments with it. But nevertheless, I might still use C++ for convenience reasons. Especially if i'm not sure to handle thing with your solution (for example UNICODE, Large and complex structures etc).

Another matter where I might use C++ is: pure power: If you ever came across a situation where you might need a UDF in a SQL-SELECT statement you might know what i'm refering to.

>If you can't do something it's not related to the language or it's features, but just because some external code expects certain conventions, which you can't control from within your tool, like certain EXE requirements for screen saver, calling conventions, etc.

Yet another reason.

Walter,