Get the user to split their current database into two... one for the data and one for the software (forms, reports, queries, etc.). Attach the data tables to the software database. Then when you update the software, you can just give them a replacement .mdb file. <p>Jim Conrad<br><a href=mailto:jconrad3@visteon.com>jconrad3@visteon.com</a><br><a href= > </a><br>
Hi Jim,<br><br>The split function does not put tables in one file, software in another. I tried it and the tables are in one, and a complete copy of the original in another. Or does it just appear that way?<br><br>alley
If your original (now code only) database contains tables with an arrow pointing to them, you were successful. These tables are just a link to the data. <p>Jim Conrad<br><a href=mailto:jconrad3@visteon.com>jconrad3@visteon.com</a><br><a href= > </a><br>
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.