>We are considering the possibility of changing an existing system to C/S. Pressumably for Microsoft SQL Server, but I believe that doing the upgrade, it should be possible to make it flexible enough so that the database can be on virtually any database server.
>
>I have never done this before, but from some reading, I believe I have an idea of what is required. For now I don't want specific technical details, but just a time estimate from people who have done this before. I haven't seen the system in detail yet, but I will make a few assumptions:
>
>

About 140 tables.
>

The system has about 100 forms - between data forms and forms for reporting options.
>

Parts of the system were programmed with Visual ProMatrix, and we will continue using Visual ProMatrix. However, I think it is safe to assume the previous programmers did not make full use of all VPM capabilities.
>
>Any estimate - even if it covers a wide range - will be appreciated.
>
>I had given a preliminary estimate of "weeks or even months". My main concerns are that commands that rely on permanent indices (such as SEEK) can no longer be used, and that a USE for a large table will have to be redesigned to fetch only a subset, for efficiency reasons.
>
>TIA,
>
>Hilmar.

Hi,
I know nothing of ProMatrix but it sounds as if the direct use of VFP tables (and VFP table-related functions) exists at all levels of the application.
My gut feeling is that it would be quicked/easier to re-write the whole app than it would be make it back-end flexible (of course with well-designed n-tier the new application could be).

I'll stay away from the argument of whether VFP is still a good option for the front end :-{
Regards,
Viv