Split DB, Replicate or UpSize?

[Guest]

I have a database that needs to be put on our company's intranet (We run an
SQL server). I would like to be able to protect my code, queries, & designs
of reports/forms as well as enter the updated info into the table & have that
info automatically update the reports.

My thoughts are to put the table in one folder on the intranet & have the
reports, queries, code & etc... in another folder. Is this possible & if
so-HOW?

Thanks!

 

[Scott McDaniel]

You can protect your forms, reports, and modules by distributing in the MDE
format. This basically strips all human-readable code and saves it in a
format the machine can read, and disallows users to enter design view for
the objects mentioned above. If you want to protect your tables and queries,
you'll have to implement User Level Security (FAQ here:
http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp)

You can put your backend in one folder and your frontend in another (this is
very common), but it won't provide any form of protection. Note also that
users will have to have read/write privileges on these folders, so any user
who has these privileges could, of course, simply copy the files to their
desktop.