>>
>>So the Table File Structure topic got me thinking... How about changing the header structure in the destroy of the data_space object so the table wouldn't even be reconized by VFP, Dbase or other applications and then changing the header structure back on the startup of the data_space object.
>>
>>Just thinking of an extra layer of protection for the data. Any comments?
>>
>
>That's fine, except that whenever someone has the header opened to permit the file to be accessed within the app, it's normal to the world, and gawd help you if you do something to the file to make it non-standard while someone else is using it...

Ed,

You have to remember this is client-only data. When the application creates an instance of the data_space class the first thing done would be the restoration of the table header. The table is then opened exclusively by the data_space object. When the data_space object is destroyed the table header would be modified so not to be recognizable to any other application. The data is never shared between users; it belongs to one client.

Well just a thought on the possibilities using VFP in non-traditional ways to achieve powerful distributed applications.

Everyone is talking about thin clients is the way to go. The reality is hardware is cheap and all my clients have 300 and 400 Pentium II with 64 to 128 Meg on their desks. I am investigating ways to use that processing power to reduce the amount of traffic between the client and server but still offer a rich, sophisticated interface users have grown to expect. I really believe VFP is the perfect tool for the job.

Bill