Yes, conceptually, that's a valid way to create a blank, distributable copy of a finished db. Just be careful not to clear tables that contain required reference or configuration data like cities/countries, configuration/settings etc. If the database is split, keep separate backups of the frontend and backend, and maintain a clean development master copy as well as a blank template.

Thank you for the advice and help.

Another option, that will create a cleaner "blank" .accdb file (split or single) is to create a new .accdb, then import the objects that you want. There is an Options button on the Import Objecs window, that will let you import only definitions and not import relationships for tables. Then you don't have to worry about extra Access hidden stuff coming in from your development file that may later cause problems. Then bring in the tables with data that you want to keep, like control and universal data (think postal codes and form parameters).  I use a set of subroutines to save and restore relationships.

Then you can also bring in just the queries, macros, modules you want. Compile and see what's missing.

A Toykan is right. Making a copy, deleting the transactional data, and then running Compact and Repair is a perfectly reasonable way to create a blank template database. Just make sure you preserve any lookup, reference, setup, or configuration tables that the database needs in order to function.

Thomas's approach is also excellent if you want to build a very clean "release" version from only the objects you intentionally want to distribute. That can be especially useful after a database has gone through lots of development and experimentation.

For most people, I'd keep at least three copies:

1. Your working development copy, with your current test data.
2. A full backup copy, with real data.
3. A clean blank template copy, with only the required reference/setup data.

If you plan to share it with other people, definitely split it first. Keep the blank backend with the tables, and distribute a separate frontend containing the forms, reports, queries, and code.

See: Reset Database

Thank you very much I think I may understand how to do it cleanly. Reset Database I will watch and see what I learn. Thank you all...