Creating new .mdb by importing tbls, qrs, frms, rpts, & mods from other .mdb

[April]

Hi,

We have a .mdb application that has become very huge and
seems to load/run rather slowly. Compacting/repairing
doesn't seem to make a difference. So we tried to create a
new .mdb and did a "Get External Data" on Modules, then
Tables, then Queries, then Forms, then Reports. All seemed
to be going smoothly until almost every attempt to import
reports (all at once, or even in groups of 3's or 5's)
resulted in an error either "Name conflicts with existing
module, project, or object library" or "Could not start
transaction, too many transactions already nested".
Oftentimes, it looks like the reports were imported, but
none of the associated VBA code gets imported, and often
when I close this new .mdb and re-open it, the reports are
gone again. The reports worked fine in the original .mdb
(albeit, slow); but there really shouldn't be any reason
why we can'r recreate a "clean" .mdb from an existing one.

Thanks in advance for any assistance you can provide on this.

April

 

[SA]

April:

Have you tried Exporting from the original db to the target db?

 

[April]

Steve,

Thanks, that seemed to do the trick. However, I had to
export some of the items more than one, they appeared in
the new db, then disappeared after doing a compact/repair.
I haven't tested absolutely every form/report yet (it's a
big project), but cursory testing seems to show good
results. Do you have any idea why Importing as opposed to
Exporting isn't working? Also, I had to manually Export
each object (table, query, form, report) individually - for
future reference, is there a way to do it more in bulk or
automate the process?

April