splitting databases

  • Thread starter Thread starter annie
  • Start date Start date
A

annie

I have a database that has all of its tables, queries, forms, and reports in
one file. I understand that Access provides a way to split off the table
objects into a separate file. By making this file inaccessible to users,
one can prevent them from modifying the design of the tables.

I would like to take this one step further and have the isolated file
contain not just the table objects but also the query objects. And I would
like the file that the users have access to to only contain forms and
reports (with no ability for them to create their own queries). This would
allow me to control how users access and manipulate the data. Does anybody
know if this can be done?

Thanks!!!
 
I would like to take this one step further and have the isolated file
contain not just the table objects but also the query objects. And I would
like the file that the users have access to to only contain forms and
reports (with no ability for them to create their own queries). This would
allow me to control how users access and manipulate the data. Does anybody
know if this can be done?
Click to expand...

Split the database into tables in the backend, and
Forms/Reports/Queries in the frontend. Then convert the frontend to a
..MDE file (Tools... Convert). KEEP THE MDB FILE! You'll need it if you
ever want to do any other changes; but the MDE is in a compiled state
which will prevent users from messing with your code, your forms, or
your reports. They can still create or change queries however; to
prevent that, implement Access Security and deny them design
privileges.
 
I didn't think that the splitter allows that. I'll give it a shot though.
Thanks John!!!
Click to expand...

The splitter wizard splits the database into two .mdb files; you would
then subsequently, in a separate operation, convert the frontend into
a .mde file.
 
Back
Top