securing a database for distribution.

  • Thread starter Thread starter J.Bennett
  • Start date Start date
J

J.Bennett

I posted this question in the "Security" section but received no response.
Any assistance would be appreciated.

I have developed a database and want to provide it to other companies to use.
I do NOT want anyone to have access to make changes to the forms, reports,
queries, etc. I simply want them to be able to run the program. They will
need to be able to enter custsomer data (which enters into the customer
table).

In my research, I have found that a runtime version can be created by simply
changing the file extension from *.accd to *.accr . However, it gives me
very little confidence as I am sure other know to simply change the extension
and you can gain full access to all of the tables, forms, reports, etc.

Can anyone give me any guidance on how I can distribute this database while
ensuring the integrity will not be compromised? Any guidance/direction
would be appreciated.

Respectfully,
James Bennett
 
J.Bennett said:
I posted this question in the "Security" section but received no response.
Any assistance would be appreciated.

I have developed a database and want to provide it to other companies to use.
I do NOT want anyone to have access to make changes to the forms, reports,
queries, etc. I simply want them to be able to run the program. They will
need to be able to enter custsomer data (which enters into the customer
table).

In my research, I have found that a runtime version can be created by simply
changing the file extension from *.accd to *.accr . However, it gives me
very little confidence as I am sure other know to simply change the extension
and you can gain full access to all of the tables, forms, reports, etc.

Can anyone give me any guidance on how I can distribute this database while
ensuring the integrity will not be compromised? Any guidance/direction
would be appreciated.

Respectfully,
James Bennett

http://support.microsoft.com/kb/132143
Mike
 
Back
Top