How to Rip out a Module gone bad

  • Thread starter Thread starter Mark C
  • Start date Start date
M

Mark C

Hi

Ocassionally I have a module / form going bad through compact/repair or
whatever, (I don't know but I'm mad that it does), however I have yet to
find a way to rip the module out of the mdb file to allow me to replace it.
Objects get stuck in the MDB file and create more corruption as they stay
since the project won't compile etc.

/decompile doesn't improve matters
compact & repair seems to create more problems than it solves

they cannot be deleted, with a number of errors including NEtwork Error,
File not Found,

HOW DO I GET THIS RID OF DEAD OBJECTS

Thanks



.................................................................
Posted via TITANnews - Uncensored Newsgroups Access-=Every Newsgroup - Anonymous, UNCENSORED, BROADBAND Downloads=-
 
I do migrate my objects, but if a form goes bad on me I have 100 other
forms, 30 reports, macros, modules and a couple of dozen tables that have
to be migrated.

Even using groups in security it takes a good couple of hours to migrate
all objects, and the security, then to rebuild / re-import the objects on
top of that.

It can be argued that since I am developing still regular backups and
falling back a couple of hours is more productive, but I have no way of
checking the work done in that time so I have to go forwards and not back

Given it is safer to move on and re-import, is there any way to rip out
reference to an object from the SYS tables or the like to go forwards??

Thanks for your help so far.
Mark

Mark,

Whenever you experience a corruption, I recommend transferring all
your non-corrupt objects to a new database.

Regards,
Graham R Seach
Click to expand...



.................................................................
Posted via TITANnews - Uncensored Newsgroups Access-=Every Newsgroup - Anonymous, UNCENSORED, BROADBAND Downloads=-
 
The import/export can, of course, be done programmatically. That would be
some very simple code... you insert the name of the corrupted object and
don't even try to copy it, of course.

Larry Linson
Microsoft Access MVO
 
You can script out the object permissions using code if
you have implemented User Level Security. You will find
MVP Sandra Daigle's code utilty can do all of this in a
blink of an eye. It works very nicely if you have to
import objects from a secured database into a new
container, but want to retain all the permissions.

You can find it here:

http://www.daiglenet.com/MSAccess.htm

Look for DbUtilities1.0 and DbUtilities1.1
 
Hi

That looks promising, I'll have to have a play to see how I get it into
the project as running it from without results in a invalid permissions
since it doesn't have the mdw rights.

Does look good though, so thanks.

I don't suppose you have any ideas as to why objects get corrupted and if
there is any way to test an object for corruption other than trial and
error on the entire file to see which one doesn't work as expected, since
the error messages are global and as usual, amazingly non-descript :)

Mark
 
Mark C said:
Hi

That looks promising, I'll have to have a play to see how I get it into
the project as running it from without results in a invalid permissions
since it doesn't have the mdw rights.
Click to expand...

You can join your mdw, and then run it.
I don't suppose you have any ideas as to why objects get corrupted and if
there is any way to test an object for corruption other than trial and
error on the entire file to see which one doesn't work as expected, since
the error messages are global and as usual, amazingly non-descript :)
Click to expand...

Help with corruption:

http://rogersaccesslibrary.com/Otherdownload.asp?SampleName='Fix Corrupt Access Database v3.2'
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Browne has some good tips on avoiding corruption at
http://members.iinet.net.au/~allenbrowne/ser-25.html
 
Back
Top