Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Risk

Status
Not open for further replies.

austen

Technical User
Nov 12, 2008
14
GB
I'm going to link two databases together. Database A will become the common front end and database B will have its form imported into it. The linked table manager will link both sets of data together etc.
What I need is a way of assessing the risk - ie that the data has not changed due to import, other than just looking from one to the other...
Does anyone have any ideas please?
Thanks,
A...
 
When you link two databases, you actually link the data tables. The front end does not contain a copy of the tables. The front end only contains links to the tables in the backend database. The data is not imported into the front end.
 
The only risk -to the data- would be that both original sets of TABLES include one or more commmon names. These, although not necessarily corrupted will be difficult to handle nad all other objects will need to be reviewed (and corrected) to distinguish the propper reference.

You mention that " ... database B will have its form imported ... ", which seems to imply that this form is the only object -other than table(s)- which will be retained in the composit database, however you need to be sure that the form does not references and queries, modules (procedures which are NOT in the Code Behind Forms") or macros (assuming that tdb "B" does not use "Pages"). Otherwise, these objects need to be reviewed to see it they conflict with similarle named objects in db "A".



MichaelRed


 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top