Hiya Jess:

BTW, I'm John and not Josh ;-)

I think that the basic DBF format was around a long time before integrated database security was an issue and --maybe-- MS is concerned about blowing away backward compatibility by an integration of security into tables. That being said, there is no reason why, with judicious use of encryption, triggers, and stored procedures, that you could not devise a pretty nifty security system at the table/database level on your own. Heck, you could even call the appropriate WinAPIs to integrate security with NT or Win95/98.


>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.