DB is done, should I rebuild using a new mdb?

[XP]

Using Office 2003 and Windows XP;

I have a DB on which I just finished initial development and it tests well.

During development, as you might suspect, I created forms and deleted forms;
created tables, and deleted some tables as the concept was perfected,
adjusted, etc.

This may sound ridiculous, but I was thinking that it may not be a bad idea
to rebuild the DB from scratch using the perfected prototype as a model. That
way I would only add the exact objects I need and copy in only perfected
code.

Apart from the process being a pain, I can't help thinking that this might
yield some sort of gain on the DB, make it's initial size more compact, for
example?

Also, I know that there are a limited number of objects you can create in
MS-Access (although I know I'm no where near reaching this). It seems I had
read somewhere that even if you delete an object, MS-Access still counts that
object even though you deleted it (could be urban legend?).

Any thoughts or ideas on the idea/concept of a scratch rebuild? Is it just
crazy talk?

Thanks much in advance.

 

[Jeanette Cunningham]

Hi,
just create a new blank database and import into it all the tables, queries,
forms etc that you want.
In the process your new database will be smaller and only contain the
objects you import.

Jeanette Cunningham

 

[Marshall Barton]

Using Office 2003 and Windows XP;

I have a DB on which I just finished initial development and it tests well.

During development, as you might suspect, I created forms and deleted forms;
created tables, and deleted some tables as the concept was perfected,
adjusted, etc.

This may sound ridiculous, but I was thinking that it may not be a bad idea
to rebuild the DB from scratch using the perfected prototype as a model. That
way I would only add the exact objects I need and copy in only perfected
code.

Apart from the process being a pain, I can't help thinking that this might
yield some sort of gain on the DB, make it's initial size more compact, for
example?

Also, I know that there are a limited number of objects you can create in
MS-Access (although I know I'm no where near reaching this). It seems I had
read somewhere that even if you delete an object, MS-Access still counts that
object even though you deleted it (could be urban legend?).

Any thoughts or ideas on the idea/concept of a scratch rebuild? Is it just
crazy talk?

Sounds like a lot of work for little gain.

Before doing anything else, make sure you have a good backup
copy of the database.

You can reclaim the space used by deleted objects by
Compacting the database (Tools - Database Utilities menu
item).

A very important step before letting other people (or even
yourself) use the database for real is to split the databse
into a back end with all the tables and relationships and a
front end file with everything else and links to the back
end tables. The Database Splitter utility will do this form
you. This is essential to your sanity when you want to
modify a form, report, query or any code and make it
available to others.

 

[John W. Vinson]

This may sound ridiculous, but I was thinking that it may not be a bad idea
to rebuild the DB from scratch using the perfected prototype as a model. That
way I would only add the exact objects I need and copy in only perfected
code.

I'd be inclined to say that it's worth the effort. Be sure that you turn Name
Autocorrect *OFF* in the new database first (and leave it off; that feature is
known as Name Autocorrupt in some circles). Marshall is right that compacting
and splitting are Good Things To Do - but IME compacting doesn't do as good a
job as importing things into a new database.

One downside: if you have workgroup security defined on objects in the
database, you will need to reestablish security on the imported objects
(either manually or by writing code).

John W. Vinson [MVP]

 

[XP]

Thanks so much to all who responded; I learned something from every reply
and will apply your suggestions.