I will say to start an application is VFP is a pain. When I was working in it we had a framework written by several of us that made it much easier. And if the application wasn't setup correctly to begin with it would cause real problems. One of the main difficulties I saw was the dev environment was not separated from the runtime when it came to the database connections. So you could easily open a database or able during dev and your exe would expect that database or table to be in the same path when it ran. That was a major pain in VFP.

Jack Allread

Again, you are deciding that a programming environment bad based on the design of one programmer!!

Jack

That is just one way that programmers designed FoxPro databases. Another reply stated that SQL Server must have a similar method that is just hidden. Keep in mind that I found Visual FoxPro (VFP) to be a very productive environment to work in for a medium sized client server app. And, from what I understand, the search algorithm (modified b-Tree) used in VFP was adapted later by SQL Server. I find it very annoying when programmers evaluate a programming language without looking at the context it was designed to be used in. Or without even trying to understand how the language was designed, so the programmer can use it effectively. It definitely seems like a form of language discrimination - operating from fixed ideas of the one programming language the person knows instead of taking time to actually figure out the most effective way to use the new one.

Jack

OK, that is wicked cool!

Jack Allread