>Jess:
>
>>
>>Due to economic concern Menachem. That's the reason why we are asking MS to include Basic Security on VFP DBC/Tables. And we want native VFP data for speed purposes.
>
>When there are economic concerns and some security is needed, why not use SyBase SQL Anywhere as a back-end? It's cheap. Or rely on o/s security as in NT for app access.

A lot of options Josh. But if you look at my original posting, we are just concern and questioning why MS is not putting into priority the need to include that basic security on native VFP database/tables. They did it in ACCESS, and Borland (Inprise) in dBase/Paradox also do. We need absolute answer, and not redirecting it into something that is not related to the question. The big question is: is it possible to do in VFP or not. If not, Why????

We do not questioning VFP's capability when it comes to remote access. We just want it to be more interesting, appealing, and saleable as an individual package (VFP alone) apart from any other third party products.