John,

>>I think he is implying that VC++ can do stuff that neither VFP or VB can do. That's what makes it worth looking at...not that it's easier to use.
><
>
>Ahh.. OK, perhaps Walter could shed some light on things C++ can do that VB cannot. On more than one occasion, I have heard the comment from some hard-core C++ guys that have said that a lot of programming that goes on in C++ would be better served in VB. Other than a full OO implementation, and the ability to write stuff like device drivers and such, I can't imagine from a business application standpoint what VC++ could do that either VFP or VB could not do.

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.

There are lot's of very interesting API's out there. For examples of things C++ can do and VB can't, See the Focus.fll library of pat boens.

Even if VB could do this just as easely as C/C++, the libraries written in C/C++ are very fast and small.

Walter,