Upload New Data Structure

[Erica]

Is there a way I can upload a new access database structure without
overwriting all of the data inside the current database?

 

[John Vinson]

Is there a way I can upload a new access database structure without
overwriting all of the data inside the current database?

Your best bet is to use a "split" database: one .mdb file containing
only the tables (the "backend"), with a separate .mdb or .mde file
containing the Forms, Reports, Queries etc. with the tables linked to
the backend (the "frontend"). The database splitter wizard will set
this up for you.

With this design you only need to give each user a new copy of the
frontend, relink the tables if necessary, and off they go; the data
stays in the backend, untouched.

It's a MAJOR pain if you have not done so. You'll need to open (each!)
user's database and use File... Get External Data... Import to import
the changed forms or reports, delete the old versions, rename forms
which got a 1 appended to the name because it would have been a
duplicate, etc. etc.

John W. Vinson[MVP]

 

[Sam]

Can you use the splitter to give access to only certain forms and reports to
users? If so how?
Thanks!

 

[John Vinson]

Can you use the splitter to give access to only certain forms and reports to
users? If so how?
Thanks!

Sure. You can give Fred a frontend database with one set of forms and
reports, and Janet a frontend database with a different set, and
Alfredo a frontend with everything. They can all be linked to the same
backend.

Makes for more maintenance work on your part but it's certainly
possible.

Alternatively, implement Access Security on the frontend and assign
permissions to user groups. Read the Security Whitepaper from
Microsoft's website. Read it TWICE... *carefully*. Then follow it TO
THE LETTER. It's not hard to do security right, but it's also pretty
easy to do it drastically wrong!

John W. Vinson[MVP]