How To Test and Update Query

  • Thread starter Thread starter mtonkovich
  • Start date Start date
M

mtonkovich

Dear NG - Is it possible to "test drive" an update query before "buying
it"? I'd like to see if it is going to work before I make the changes
permanent. And yes, I have little confidence in myself at this point!

Mike
 
My question is:

Do you not think it would be wise to make a copy of your database and
test your queries on that? That way if you "accidentally" screw up,
nothing is lost. Never, never, never test new things on a live
database.

On another note, the answer to your question is:

Yes, use Datasheet View. The query doesn't update until your click the
"!"

Cheers,
Jason Lepack
 
*ALWAYS* do your development work on a test copy of your database and never
on a production copy.

Also, it is a good insurance policy to keep copies of your database backed
up at regular intervals.
 
Jason,

Thanks for the help. I have been working on a backup copy of the db.
If the update doesn't work the way that I planned, I just copy the
original and start over. I just thought there might be a more
efficient means for testing the update query.
 
Van,

As I mentioned to Jason, I am working on a copy of the original
database. Thanks for the heads-up!
 
OK ...

1. Make sure the logic you use is correct.
2. Test only a small sample data set (so that you can look at the data and
note down which records should be updated) but it must include border cases.
For example (simplified), if you want to update where Field1 is less than
100, include value like 99.99, 100.0, 100.01, etc ... After update, check
and make sure that records that should be updated are updated and records
that shouldn't be updated are not updated ...
3. Implement ... and be confident! <g>
 
Back
Top