What happens when you re-import everthing?

[waldemar]

Isnt it a common procedure to reimport all tables, queries, forms, macros, modules, etc. into a fresh, new MDB once in a while. I find that it reduces the size most of times by 50%, probably getting rid of some ex-code that Compact&Repair Database obviously cant remove...

But I find it can corrupt the code somehow. With my newest database the complete reimport doesnt work without strange errors/differences in the application.

The question is: Should a newly reimported version work? (This would mean that in my current version I have programmed workarounds around bugs/behaviors that exist only due to the amount of past coding? sort of "Ballast"...?)
Or does Access "forget" to import some stuff, so that the could does not work *any more*?

Anybody having experience with this?

Regards
waldemar

 

[Paul7905]

I have had to create a new, blank database and import everything from the database I am working in and usually am forced to do this because for some reason, Access will do two strange things :

1. Suddenly stop recognizing breakpoints set in the VBA code window. '

2. Stop prompting me for whether or not I want to "save changes"

Most recently, when doing this, I noticed that my database, after importing, was three times the size that it was prior to importing. Curious as to what what causing this, I imported each section seperately (table, queries, forms etc etc, noting the size of the new database after each import. The tables section caused the "bloating" and this seemed strange as it consisted only of links to a backend database. I decided to play around with it a little and it turned out that importing the tables prefixed with "Mysys...." were causing the new frontend database to become extremely large. I re-did everything and left those out of the import and everything was fine and the new database was much smaller (i am using access200)

I have never had things cease to function after importing to a newly created database, it only restores the functionality lost in vba debugging and the prompting for saving changes.

paul

 

[waldemar]

Strange, I had (fortunately not right now) the problem that after a reimport re-build, afterwards access crashed whenenver I saved *anything*!.... on another PC it worked... I assume this is due to problems with earlier service packs and earlier JET versions...

When I create a reimport rebuild, access finds more compilations errors! This is interesting... Compiling all worked fine before, but in the fresh,new MDB the vba compiler finds *more*!!.....

Usually I disable the view at the Systemobject.... what is default in the import, when I choose all tables.... are the system tables imported or ignored?

Regards
waldemar