>>Hi Bob...
>>
>>Is this an issue with VFP - or is the issue with the implementation you have selected???
>
>You know what I think is wrong with VFP? Too many of "us" are writing things under the heading of "What's wrong with VFP?" instead of writing things like "VFP is a wonderful database environment!" Just my .02 worth!

In a twisted way that was my point. I have used fox for years and years. I used DBASE II and III+ before that. When Dbase IV came it was a lot of trouble. Over the years, in DOS or Windows, I found I could always depend on finding a way to solve any problem I was faced. Fox seemed to provide multiple ways to solve any problem at hand. Work arounds were far and few between. It was and is a joy to program with. It has never let me down.

Other tools I use (VB) and have tried (Powerbuilder) are a much bigger pain in the ass. Maybe my mind works better with the VFP model. Maybe if the VFP developers were smart they would have removed that stupid global error handler and required us to code an error statement in every method and function. Just like the big boys get to do.

Do you realize how difficult it is to prove a program is very complex if the error handling is so smooth? People appreciate your talents much more when a VB program blows up because of deficient error handling. They realize how difficult it is to get things to work. It is much harder to show them that when you use VFP.

When people ask me "Is that going to be difficult to do?" I sometimes answer, "Well, if you want it to be difficult, I won't be able to do it in VFP. I'll have to switch to VB."