Everything has a price and your client must accept that security has a high price tag (read client-server).

In fact, yes, you are asking much. Preventing unautorized access to the database will require, IMHO, a big change in the way VFP work with databases. You can add security to your database by using a third-party encrypting tool, like Cryptor.

---

>I've tried understanding MS POV re: marketability of SQL Server by not enhancing VFP Database Security. But to my disappointment, lots of clients simply do not understand no matter how hard we explain to them about this. Client Server is oftentimes not a smart idea on small businesses because of budget constraints. COM, DCOM using VFP tables can be a good option but it needs a total rewrite on the existing application specifically those which has been implemented. We are not asking too much: just a little bit security on the Native VFP Table.