Alex,

I'm interested in using alternate access credentials to access data rather than mapping data directories to a drive letter under the users account. I understand this is possible under XP but I'm not sure how I would do this under 2000.

I'm assuming that I would configure the EXE so it runs under specific credentials. Then when the EXE launches only that process would have access to the data and the user could not access the files through explorer. Is this correct? What are the steps involved in setting this up under Windows 2000 professional?

Greg
>>Not to jump on you but I've had several people on here say encryption solves security problems when it really just stops prying eyes, not those that just want to do damage.
>
>Entirely correct. After encryption you still have the problem of access to the data. Encryption does nothing against someone corrupting your dbf, zapping it or just erasing the files. To avoid that problem in a file-based system you would have to play with Windows Access Control, from an administrator point of view. This of course still may leave some security holes, not to mention the Domain (Windows) Admin still has access and can do damage.
>
>From a security point of view, SQL Server (or similar) is much better, which was I believe CB's point, as you can as a DBA secure the data even from a SysAdmin. (Now the DBA is the security hole <g>).