C
Chuck
I have built and am supporting a database for a non-profit group. It is
presently configured in 2 db's ... a front-end and a back-end. The
back-end, naturally, has all the dynamic tables. Since the developement is
ongoing, the databases are sent back and forth via email. Most often I send
her just updates on the front-end but there are times when she needs to send
both db's. Herein lies the problem. She often restores one or both of the
db's to the wrong directory and either the links to not work ... or worse
yet, she puts the back-end in the wrong directory and proceeds to store data
in the wrong back end.
Is there a way to compartmentalize the tables from the front-end code in
*one* db? If so, then I could send her one merged db, continue to develope
the front-end, and easily swap, periodically, the program code before
returning the db.
Any suggestions would be appreciated.
Chuck
presently configured in 2 db's ... a front-end and a back-end. The
back-end, naturally, has all the dynamic tables. Since the developement is
ongoing, the databases are sent back and forth via email. Most often I send
her just updates on the front-end but there are times when she needs to send
both db's. Herein lies the problem. She often restores one or both of the
db's to the wrong directory and either the links to not work ... or worse
yet, she puts the back-end in the wrong directory and proceeds to store data
in the wrong back end.
Is there a way to compartmentalize the tables from the front-end code in
*one* db? If so, then I could send her one merged db, continue to develope
the front-end, and easily swap, periodically, the program code before
returning the db.
Any suggestions would be appreciated.
Chuck