this is pretty much one of those "learn by doing" things; you get (somewhat)
better a testing a db each time you build and test one. document your code
and/or macros well, and make sure you have good error handling in your code
(no way to do that with macros, AFAIK). test it yourself by using it in
pseudo-production mode, of course, but beware - it can be difficult to
thoroughly test your own design, because you already know the "right" way to
do everything, so you tend to not make mistakes that can cause problems,
even when you try to. it's a really good idea to "field-test" your db with
actual users *before* you deploy it for production use - they'll invariably
find errors you never thought of! and just resign yourself to the
probability that no matter how diligent you are, somewhere down the line
somebody is going to do something that causes an unidentified error.
hth