Production and development versions of my database update each other

[Crusado]

Hi

I keep the production version of my database on a server, and a copy of it for development work on my desktop. Today I've made several changes to the development version, which didn't work. I then opened the production version held on the server in a separate MS Access window to compare the queries/results to see where the problem was and have found that the changes have automatically updated in the production version. Can anyone explain this? They shouldnt be linked at all. The 2 versions both link to a datawarehouse through an ODBC link, but shouldn't be linking to each other (I'm using Access 2003).

Cheers

 

[The_Doc_Man]

If the changes were to the code, you are right that they should not have shown up. But if you opened the database via an ICON, right-click the icon to see where it is pointing (in the properties dialog box segment that shows you the command line equivalent of what you are doing.)

If the changes were to data, I would say that your copy of the database still points to the same ODBC port on the server regardless of from where it is running.

 

[Crusado]

I made changes to code and to data held in tables actually in the database (not the datawarehouse ODBC link).

I always open the mdb by navigating to it in windows explorer, so it's not that a shortcut was pointing to the wrong version.

I wasn't using the "Backup Database" option to create my starting development DB, I'd just find the prod version in explorer, copy, navigate to my desktop and paste and rename it. Wondered if doing it this way meant that Access linked the tables and queries is some way?