I'm growing concerned about security issues with my multi-user application. Users can double click through Windows Explorer and open files. Even worse, they can delete tables or the entire directory. I don't see any useful way to restrict permissions in Windows or use the table password feature in Paradox to help with this, so I started thinking about a database server.
If I understand correctly, I could set up the BDE on the client machines to access the data through ODBC. Is it then possible to set up the ODBC server on my W2K fileserver, grant directory permissions to the account that's running the ODBC server (would that be the system account?), and deny permissions to other users?
What software can I get to act as the ODBC server? Can the BDE do that? Will I see a serious performance hit by inserting yet another layer of middleware? Is ODBC the best way to go about this?
-John
If I understand correctly, I could set up the BDE on the client machines to access the data through ODBC. Is it then possible to set up the ODBC server on my W2K fileserver, grant directory permissions to the account that's running the ODBC server (would that be the system account?), and deny permissions to other users?
What software can I get to act as the ODBC server? Can the BDE do that? Will I see a serious performance hit by inserting yet another layer of middleware? Is ODBC the best way to go about this?
-John