PDA

You are currently viewing a search engine-friendly (archive) version of this page.

View Full Version : Access 97 App - Creating Test Environment


sassyt
October 10, 2001, 01:33 pm
I am responsible for changing a few calculations and column in an application. I would like to know if it is possible to create a copy of the app/database to work on. Sort of a test environment. How do I do this? What should I look for?

tweakthis
October 10, 2001, 06:31 pm
Sure you can. Hmmm, well, at least you can with Access 97. What database are you using? Do you know the folder the database is stored in? If yes, then go to start ->> programs ->> windows explorer. Find the database and copy it to another location.

To ensure that's it's not just a shortcut to the original, then check the size against the original database. To be on the safe side, you can even re-name the copied database so you don't get confused and muck up the original. I keep all my databases in a folder called, ta da, database. So if I do that (copy) procedure, then I move it back to my database folder so I don't get confused about what is where and what I can delete.

BTW, if you don't know where the database is stored (if you only click an icon to open it), then open the database and try this: from the top menu, click file, database properties. Hopefully that will tell you where the file is stored.

Hope that helps. Let me know if it's too confusing.

[ October 10, 2001: Message edited by: tweakthis ]

sassyt
October 19, 2001, 10:09 am
Thanks for you help. There is one additional thing. The database is an application and has two or maybe three parts. an application, the database. The application is located in a different directory than the database. Sounds confusing huh?

tweakthis
October 20, 2001, 03:00 am
OK, if I understand correctly, the program (Ms Access 97) is stored in one location and the actual database is stored in another. Is that right? If yes, the location of the database is not important. You can copy it to another location and then manipulate it as you want. My main database is called db2 (original, eh) has the main client files, a ton of queries, reports, etc. Is that what you mean? The important thing is to make sure it's a copy and not a shortcut. That's why I say that looking at the size will tell you whether or not it's a true copy. I shortcut is usually a 1kb file. A database can be small or huge, but it's sure bigger than 1 kb. Does this help at all? Post back if I've misunderstood your message or you have more questions. Ooh, another thought, if it's not too large, you can email yourself the database to ensure you're working on a true copy.

sassyt
October 29, 2001, 12:26 pm
What about the application. Its the part that I need to test. In the application there are several forms that call and calculate the data in the database. I need to change the calculations and the names of the fields that the forms are calling. Will I be able to make a copy of the application portion and make changes there?
hmmmm
Thanks for your insight so far!!!
sassyt

jbcalg
October 29, 2001, 01:14 pm
[quote]Originally posted by sassyt:
<strong>What about the application. Its the part that I need to test. In the application there are several forms that call and calculate the data in the database. I need to change the calculations and the names of the fields that the forms are calling. Will I be able to make a copy of the application portion and make changes there?
hmmmm
Thanks for your insight so far!!!
sassyt</strong><hr></blockquote>

what is the 'application'
- is it a database form that calls from the source database?
- is it a spreadsheet or word pro application?
- what software opens when you use the 'application'?

i'm getting a little confused between the 'application' and the 'database' LOL

i use a semi complicated (because i made it that way LOL) report generator - an access dbase that is just forms, linked tables, and stats functions. the source of the data it manipulates (calls from) is a separate access database. these are linked through the linked table manager.

when testing: i copy the forms database to a new folder and rename it (ie formstest1), then i copy the data source to the same folder and also rename it (ie testdata1). then i open formstest1, and link the tables to testdata1.

that way i have a completely separate 'application' and datasource which i can screw up as best i can without harming the original one that works.

is that the sort of thing you're trying to do? duplicate an 'application' and a datasource, then change things around without damaging the original?

[ October 29, 2001: Message edited by: jbcalg ]</p>