Larry
Encrypting is a good idea. The one I have tried is called cryptor. You can get it at Hallogram. It is a fll and/or dll; you encrypt your table by supplying a password to a fll function, then when your apps need to use the table they "register" it with Cryptor supplying the password; Cryptor then seamlessly encrypts/decrypts the table automatically as you use it- you can read/write etc no problem. It also has a definable level of compression that can show visible speed differences on a WAN.
Forget about using NT privileges. Anyone who can access a table in your app can also open it in Excel. To avoid this you could create an OLE Server that uses its own security, but Cryptor is better- you don't have to redesign your whole app.
Regards
JR
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
