asked on

using visual foxpro front end and SQL Server oy MY SQL as database server

Somehow I get annoyed by the repeating question of my customer "Why you do no use a SQL engine within your applications". Actually I don't see this as a must but anyhow I would like to get rid of this question when I install new applications on my customers. Did anyone changed their apps from free tables to SQL server or MySQL? Can you give some directions on the approach I should follow. Besides all I stated there are some issues when I work with distributed environments, namely, the access to shared drives within a WAN it is not so consistent as it could be.
If someone could give me a help, I would be grateful
Regards
Lucilia

ASKER CERTIFIED SOLUTION

Cyril Joudieh

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

rinfo

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Olaf Doschke

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

dportas

There are lots of good reasons to use a server DBMS: Resiliance; High availability and security features; Read consistency support; Scalability; More cost effective and manageable in a large enterprise network and service based environment; Easier to share data; Better support for third-party application integration, reporting and analytical software.

As a general rule, any non-trivial, multi-user database these days really ought to use a client-sever / N-tier architecture unless there are very good reasons not to. VFP makes a fine front end for client-server / N-tier apps. Obviously the limitations of 32bit VFP and its end-of-life status will rule it out for many people.