Confidential Data

[Guest]

I am developing a database for an employee assistance program that will contain confidential information. I will not be utilizing the database, input ing any data, etc., just developing it. I will have to make structural chabges to it periodically, create reports, querys, etc., but wont be able to test it with its own data

I now how to import/export things, but does anyone have any tips on the best way to make changes to a database under these conditions? I am reating a copy of the database without data that is structurally identical

Thanks in advance

DEI

 

[Larry Linson]

You use a split database: a back-end with tables and their data and
relationships. The/each user gets a front-end of queries, forms, reports,
macros, modules, and any rarely changed lookup tables. You use the Linked
Table Manager, when needed, to relink if you move the back end to a
different folder. There is even a DatabaseSplitter built-in to assist you.

Since the real, live data is so confidential, you can have another
identically-structured development database with test data to use when you
are testing and developing.

Larry Linson
Microsoft Access MVP

I am developing a database for an employee assistance program that will

contain confidential information. I will not be utilizing the database,
input ing any data, etc., just developing it. I will have to make
structural chabges to it periodically, create reports, querys, etc., but
wont be able to test it with its own data.

I now how to import/export things, but does anyone have any tips on the

best way to make changes to a database under these conditions? I am reating
a copy of the database without data that is structurally identical.