Hi,
I have an app with VB as front-end and MS-Access as back-end. Now when I would deploy the app, I do not want anyone to open the database using Ms-access and view the table structure. So I decided to password-protect the database. But if the database is password-protected and I try to give user-id and password using VB's connection string, it gives me error saying either the database is opened in exclusive mode or use workgroup file.
I have following questions:
1. Is using system workgroup file the only way to secure my database?
2. If I create this file, I think I also need to distribute it. Am I correct?
3. If I distribute it and the client already has system workgroup file for some other app, then my file will overwrite the client's existing file. Any solution for this?
4. If I distribute my app using Installshield, can I just deploy the system workgroup file or does it need manual configuration?
Please advise.
Regards,
Vilas
I have an app with VB as front-end and MS-Access as back-end. Now when I would deploy the app, I do not want anyone to open the database using Ms-access and view the table structure. So I decided to password-protect the database. But if the database is password-protected and I try to give user-id and password using VB's connection string, it gives me error saying either the database is opened in exclusive mode or use workgroup file.
I have following questions:
1. Is using system workgroup file the only way to secure my database?
2. If I create this file, I think I also need to distribute it. Am I correct?
3. If I distribute it and the client already has system workgroup file for some other app, then my file will overwrite the client's existing file. Any solution for this?
4. If I distribute my app using Installshield, can I just deploy the system workgroup file or does it need manual configuration?
Please advise.
Regards,
Vilas