Test Data Question

[vanessa03]

I am new to programming in Access 2003. What is the perferred method of creating a database, but continuing to develop more code. I want to implement part of the database, but continue to work on the second phase. Do programmers use a test database for further programming or do you have test tables, queries, forms in the same database?

 

[PHV]

Split the database in BackEnd and FrontEnd.
You develop in your local FE.

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[vanessa03]

First of all thank you for answering. So how does that protect your tables in the backend database from being corrupted while you are testing forms on the frontend?

 

[MajP]

I do this with 2 backends and 2 frontends.

1 You have a backend with real data tables only
2. You have a working front end with all forms, reports, and code
3. Now copy the working backend and make a development BE
4. Make a development frontend connected to the development BE.

As you are satisfied with the way the development FE is working, replace the working front end with a copy of development front end.

Now go back and keep developing on the development FE. Each time you are satisfied with the way it is working you can switch out the working front end.

When you are developing you are always touching a copy of the real data.

 

[vanessa03]

Thanks MajP! That makes sense.

 

[MichaelRed]

a wee bit of caution ...

in development and ad-hoc work, it is possible (probable) that you will create objects (particularly in the FE) that are not really useful in the production version (FE). If you just keep copying the "approved" dev FE to the Production FE, it will grow mush faster that you may want it to.

better? to keep a list of what you really want in the FE, and just copy these to your production ver. I have created a set of procedures and a table tautomate this process, and found it to be useful. but it also r=generates additional copies of the FE and so needs to have the intermediate steps "archived".

If you maintain a simple table with a 'change name", "object name" and what ever other info you desire (adding the info each time you change an object) when you are satisfied with the overall change, you can just export the individual objects to your production version. Please note you cannot export linked tables, only the link is exported.

BTW there are several / numerous threads and / ot faqs on the topic.




MichaelRed