Creating a test environment

[Jamie Murray]

I have cerated a basic call logging database, but it is a continual state of
fluxz and development. I am keen to set up a test environment, but looking
at the manual it woudl appear the only way would be to use replicas, and
create a desing master. Is this the best way, and will it allow me to change
forms, queries, etc. and update them automatically. What should I do if I
wish to add an extra field into a table? And are there any major pitfalls.

Thanks for the help

 

[Duane Hookom]

Is you application split into a front end and back end? Adding a field to
the back end would generally suggest that all users would need to be out of
the system.

 

[Jerry Whittle]

To reduce the amount of flux and development, the best thing to do is hammer
out the business rules and requirements before starting on the database.
Sometimes this can take up over a fourth of a project; however, it has a huge
payback.

Still things change or something minor gets missed. Therefore I often add a
couple of extra text (255 characters) and number fields (double) plus maybe
currency, Yes/No, and Date fields depending on what is to be stored in the
table. Yes it's a little sloppy, but as some of my clients are hunderds of
miles away, it has made my life easier a few times.