I have shared 2 databases in 2 different folders. The databases are similar as one is used for testing and one is used for printing a number of forms. Let's call the databases PROD and TEST and lets say that they exist on a server called \\DATABASES. PROD.mdb exists in a folder called \\DATABASES\PROD and TEST.mdb exists in a folder called \\DATABASES\TEST. \\DATABASES is running Microsoft SQL Server for a number of different things on that server. When I look at Enterprise Manager I can see both PROD and TEST listed as databases. Each has the same tables. The end users and myself use 2 different ODBC connections on our workstations to work with the 2 databases.
Here's where things get weird.
The forms that get printed in PROD.mdb pull live data from an Oracle database on a different remote server. In the TEST database it's not supposed to be pulling live data but instead is supposed to require the user to create test data. That's how it used to work when it was designed in Access 2000. However, now when someone goes into TEST.mdb the table they see that is supposed to contain only test data is also pulling live data. And when they make changes to a particular form that authorizes which subsequent reports and forms are available it is also making the change in the PROD.mdb table. The OrderData table in TEST.mdb, which is where they put the manually created test data only has 35 records. Yet, when I have TEST.mdb open at look at OrderData in the list of tables it has 47,129 records, the same number that are in the PROD.mdb version.
How do I track down what's going on in TEST.mdb and keep it from crossing over with PROD.mdb? Where do I find the information that tells me where [TEST.mdb].[OrderData] is looking for its data? Unexpected forms becoming authorized and used in PROD.mdb has caused quite a ruckus to say the least.