John,

I must say, this one of your best posts to this forum I have seen in the last 3 years I have been tripping around this community. Here, here.

>The first step is in understanding what front the issue is being fought on. i.e. - is it an application tool or database issue. Sounds to me like it is
>a database issue.

Yes.

> The next thing is to analyze the premise upon which their argument is based:

> 1. single user or low-end version built on something like FoxPro or Access.
>2. a more robust, enterprise type version built on something like SQL Server.

Yes.

> Fox is not a single user databse. Fox for the most part, is a robust data engine in terms of local data performance. There is no single universally
> accepted definition of what robust is. Robust is one of those terms of art that spews out of a lot of mouths. Unfortunately, the owners of those
> mouths do not have the slightest idea of what robust is.

In many cases, true. And it is our responsibility to inform our customer base, from our standpoint/opinion.

> My guess is that your folks look at robustness in terms of size of data and security. Access has security, but it falls short on size. Fox falls
>short on size and has no security.

Oops. Falls short on security, not size, compared to access that is.

> So, is there something to this? Yet bet. There is absolutely no counter argument to Fox over SQL when size and security are the issue. Even I
> could not argue that point and win...< bg >..

True. I don't know anyone who would argue that dbf wins over a real backend data server. However, I think VFP is easily as good of a tier language as any other. In fact, if you are manipulating large of amounts of data in a mid tier scenario I would use VFP hands down. Granted, for 'me'.

> But the battle is not over yet...

Also true.

> While you may lose on the data engine front, you might win on the UI front. Fox lousy native Client Server support notwithstanding, its UI tools
> are pretty good. Depending on your scenario, you may be able to make a convincing argument on the UI side.

True.

> In summary, don't fight the battle on the database field, you will lose.

To me, VFP is the best tool for yanking data from a backend, stirring it up to your liking, and spitting it out to whatever the front end might be.

You are right. (duh) VFP is not a data server. I think this issue is what causes alot of animosity(sp) with diehard VFP'ers.

Anyway, cheers.

-E-