Hi Pat...
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.
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.
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.
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.
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 >..
But the battle is not over yet...
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.
In summary, don't fight the battle on the database field, you will lose.
As far as developing enterprise apps in VFP, again, it comes down to what the definition of an enterprise app is. In our situation, we have developed fairly large VFP apps using SQL Server. FWIW, I don't think native VFP data qualifies as an enterprise data store. So, it is a fair statement to make that to qualify, you need to be using something like SQL Server, Oracle, etc.
In your case, the issue is going to come down to how effectively can you tie together VFP and SQL Server. For that answer, I will direct you to the following website:
http://www.takenote.com/dc2000.htmGood Luck!!
< JVP >
>I have a Visual Foxpro application that a department in a corporation wants to use. However, the IT department is telling them that they don't want the FoxPro app in their environment. Here is one of their statements: "Many of these vertical market type apps have a single user or low-end version built on something like FoxPro or Access. We prefer a more robust, enterprise type version built on something like SQL Server." Is there really something to this - is Foxpro that much less "robust"? Are you all designing for enterprise environments - are there some examples I can point to?
>
>Thanks for any suggestions,
>Pat
