Hi Ron,

>
>I have a system developed in FoxPro 2.5 DOS. It has 80 screens, 240
>reports, 72 databases, the largest of which has approximately 55,00 records. It has been on ongoing development for the last 6 years. We are at the point now where we are going to run the code thru the Windows FoxPro 2.6a tranporter and then run the system in Visual FoxPro 6.0 (this is the easiest way since we have already put in $200,00 worth of work and don't want to have to re-write all the screens and reports directly in Visual if we don't have to). This system will be running on an NT network with 9 workstations.
>

Why are you contemplating any change at all? What is wrong with the current version? I assume the app is run entirely local over a lan. The volume of data is small for Foxpro.

There must be some reason to rewrite. Simply moving the app tp VFP thru a converter gets you what? To really make use of the power and features of VFP you will have to rewrite your app although many of your intricate programs can be used.

>Lately, my client has been hearing from other sources, that SQL Server 7.0 (no mention as to what the front end would be) would be a better alternative for his system for lots of reasons according to his sources: more stable environment, less costly changes, the fact that they have been telling my client that Visual FoxPro will be dead within 2 years. They have quoted him about $40,000 to re-do the system, which is, in my opinion, way off base. There are some very, very intricate procedures/programming logic in the system. I can't for the life see how this could be a better alternative for him.
>

I see nothing so far in your requirements that would lead me to suggest a SQL server solution. The volume is small, it is not distributed and you did not mention any special database security requirements.

>My question(s) for you is, do you think Visual is going to be dead in 2 years, do you think that Visual running 2.6 Windows code will be stable enough to work, what is your opinion on using SQL Server with these size databases, what are the ongoing support/other costs involved with SQL Server that maybe my client does not realize will be there in the future and any other opinions.

If I were starting this from scratch, I would still consider VFP as the prime choice for development. If the specs called for MAJOR growth including distributed access requirements then I would perhaps look towards a client server solution.

Sounds to me like you have a competitor with a foot in the door, probably a friend of a friend deal. I would sit down with your client and assess the system requirements and then rate the current system against the requirements. "If it ain't broke... don't fixit" If you find functionality, ot performance or security or whatever lacking, then compare possible solutions INCLUDING enhancements to the current system. Unless your six years of effort have been entirely off target, I would find it hard to believe that a complete rewrite would be the obvious choice.

Hope this helps,

Ken