Hi Jim,

Its been a while since we last spoke. How is life ?

>An excellent list of wishes - I'd like to see every one of them done!

Thanks. I think its time that VFPs is going to enhance on those fields that makes VFP such beutifull tool. I sure hope that in VFP 8, at least some of those would be included.

>Following this thread I was wracking my brain trying to remember where it was that I had used something similar to "2-way" in the past (excluding my dalliance with VB) and I finally remembered...

>2-3 years ago I was pushed to make a small but 'complex' app using Access. Doing so I found that I could change the factors using the interface *or* directly in the SQL. Either one reflected the other.
>While this isn't exactly as what is being described, and I don't recollect there being a .txt for the 'progam', it was awfully handy. Extending it as described here would only make it better.

I'd like to have two or more ways to do things. I always gives you an alternative if one way somehow does not work out well.

For example, how many ways are there to check if a certain record exists ?
1. LOCATE FOR
2. SEEK(), SEEK + EOF() OR FOUND()
3. INDEXSEEK()
4. LOOKUP()
5. KEYMATCH()
6. SQL - SELECT

All have different properties and behaviour. You can choose for those which fit best in a certain situation.

Some of us here, wish to get rid of much of the xBase side of VFP. IMO, this would mean the end of the tool, since there are simply to many alternatives to the SQL side of VFP. I'm happy for those guys who are more than pleased with juat an SQL-server connection, a set of SQL commands and occasionally using the VFP engine for cursor results, but to me, and I think the majority of the VFP community, that isn't enough: We want more power on the good old xBase langage and we want to extend it and lift it up to a higher performance level.

Walter,