MS Access is making things harder than they need to be
June 9, 2011 9:56 AM Subscribe
MS Access: I have responsibility for a large database in Access 2007. How can I create a dev copy to experiment with changing forms/layout/queries, etc. which shows record data, but does NOT link to and make changes to data in the tables in the "real" original database? I do not know SQL.
posted by cuddles.mcsnuggy to technology (4 answers total) 2 users marked this as a favorite
Our IT staff was laid off last month. I need to do this without SQL. I understand that I can just save a dev copy with another file name & muck around at will with the forms & layout, etc. without messing up the look of the "real" version ... but I want to also experiment with how the table data itself behaves in these forms by entering sample data and changing existing data in the records of the dev copy. So how I can create a copy of the entire DB including the tables and records, in which I can change any part of the dev copy's infrastructure or data itself, but will not change the records in my main DB? To explain what I mean: Assume the main db is titled "UserDatabase.mbd" located in a folder named Files01 on the server. I save a copy of the entire db titled "DatabaseDev060911.mdb" in a different folder named Files02 (by using file>"save as"). Now I can open "DatabaseDev060911" and goof around all I want with the forms and layout of the dev copy, and the real database "UserDatabase" in the folder Files01 is unchanged. However, right now if I change any of the *record data* or the tables in my dev copy, those records are getting changed in our main db. This is bad. How to not do this? Is there a way when copying a whole database to copy the tables & records to use as sample data so I can experiment with them, but not have that (dev) data linked to the original? This seems like it should be simple but I can't find anything in the help screens or gis on how to do this.