Public Sub code problem

[Mr. B]

Now, that's a good idea. Let me know how you come out testing like that.

 

[SOS]

Also, perhaps some corruption is creeping in and it is time to import everything into a brand new mdb/accdb file before it gets worse. (just a thought).

 

[Mr. B]

SOS,

That is a possibility, but normally, at least for me, if a form gets corrupted, it stays that way and nothing I can do will fix it.

Good thought though.

 

[SOS]

if a form gets corrupted, it stays that way and nothing I can do will fix it.

If you catch it in time it is sometimes salvageable, but it is a matter of reading the signs soon enough

 

[Jon123]

you guys a scaring me now how do I know if i have a form that is corrupted,

 

[SOS]

you guys a scaring me now how do I know if i have a form that is corrupted,

It is kind of hard to tell really, but I will usually just import to a new mdb/accdb file if I suspect something (strange happenings with no good explanation). Then if that doesn't work, I will sometimes take a copy and delete a form or report, one at a time to see if that helps. I don't keep deleting objects, but instead after deleting one and the strange behaviour is still there, I will then make another copy and delete another object and so on and so on until it seems to stabilize. At that point, when you've found the offending form/report, etc. I then will rebuild that one (but you can also try copying the form or report module to a text file and then set the form/Report's HAS MODULE property to NO and then let it delete the stuff, save and then do a compact and repair, import into a fresh database and then copy the code back to the module, one procedure at a time, after setting the Has Module property for the form/report back to yes).

A pain in the backside? Yes, you betcha. But if the form is complex it can be worth the effort to try to save it.

 

[Mr. B]

That is some very good advice from SOS.

I also have experienced corruption of forms. Not so much with 2007 as with previous versions. If you can't find any other reason for the problem, it can be a corrupt form.

 

[Jon123]

Well the testng results are in. It must have been corruption in the form.
I pulled an earilry backup and just finished doing the updates. The orginal code works fine and the dbase is no longer dumping access. So it looks like the main problems Ive been having latey were mostly do the that form. So what causes this corruption? Can it be avoided? how often should I create a new dbase and import everything back in?

jon

 

[Mr. B]

Jon,

I do not have any criteria that I can say causes the problems with Access forms. One thing that I have noticed is that if you copy controls from one form to another you can have problems getting the VBA window to acknowledge the existance of those new controls.

Other than that, I am mostly in the dark on this one.