Once the user launches the app to create the "connection" to the server location, could the user then open Windows Explorer and then have access to the database as long as the app was running?

>You do have the option of putting the Fox database on a server and securing that location with normal network security providing a single account access to it. Then store the single access account info in an encrypted manner accessible to the program. Regardless of how the user logs in to the network the program can then connect to the secured folder 'as' the account that has rights since the program 'knows' that id and password. The security is then two fold: one) securing the folder via windows and two) securing the account information within the program. I suppose you would also want to provide an administrative ability in the program to manage the access account. But this would keep everyone out of the database except via the program where it is in your control. And it works (and works well) as we've done it. The key is 'how to connect to a network location as someone else'... And, of course, securing the access info via good encryption.