Form Becoming Corrupted

[JamesJ]

This seems to happen way to often. Forms get corrupted when making
the slightest change to it.
Example: Today just for kicks I copied and pasted the form to have a backup.
The only change I made to the backup was using the AutoFormat... and bam!
Certain
fields weren't being updated properly, an unbound text box was no longer
being displayed.
And yes I checked to make sure the control's fore colors weren't the same as
the
back color. There most likely are other things that I probably wouldn't
notice unless I worked with the
form for a few more minutes.
The only solution I've been told so far was to backup, backup and backup.
This doesn't do any good when one backs up a corrupted form. I find myself
afraid to change the back color of a control let alone make some minor
changes.
AutoCorrect boxes are all unchecked.
I quess I must simply leave by db alone and don't mess with it.
Is this happening to anyone else???

James

 

[Chris O'C via AccessMonster.com]

I'd start fresh. Create a new db, turn off track name autocorrect, and
import all objects into the new db. Compile the code and compact/repair.

Chris

 

[ruralguy via AccessMonster.com]

You also did not mention which version of Access you were using. Have you
applied all of the Service packs and the HotFixes? Is this on a network? Is
it multi-user and if so is anyone else in the db at the same time?

 

[ruralguy via AccessMonster.com]

Another useful piece of info is what OS? Here's a link that could be useful:
http://allenbrowne.com/ser-25.html

 

[JamesJ]

Did that. The db I replaced appears to have less problems. An an ubound
text filed that doesn't want to display at all. Not sure if this constitute
corruption, now.
When I restored my deleted db (original) the unbound text field diplays
properly.

James

 

[JamesJ]

Access 2007 sp 1 - Vista Basic sp 1
Where might I go to check on Hotfixes?

James

 

[Chris O'C via AccessMonster.com]

I'd import the original form from the old db file and modify that to add any
additional controls and code so it matches the latest version. Then I'd
delete the corrupted form and compact/repair.

Chris

 

[JamesJ]

The backup is up-to-date. This unbound text field (txtCount) doesn't
display any data, not even #Name, when I save the form with an AutoFormat
theme.
The txtCount is a field to display the number of records (rows) being
displayed.
So, in the OnCurrent of the form I have:

Private Sub Form_Current()

Me.RecordsetClone.MoveLast
Me.txtCount = Me.RecordsetClone.RecordCount & " Item(s)"

End Sub

I discovered that this text box wasn't displaying anything for some reason
a couple of days ago after I made some changes to the form(s).The changes
at this time didn't include the AutoFormat. I imported a form from a backup
that was ok.
Don't know why this is happening. I'll have to sift through my backups (and
there are many of them)
and find the ones where this field is displaying properly.

James

 

[ruralguy via AccessMonster.com]

Here's one: http://support.microsoft.com/kb/960307

Access 2007 sp 1 - Vista Basic sp 1
Where might I go to check on Hotfixes?

James

You also did not mention which version of Access you were using. Have you
applied all of the Service packs and the HotFixes? Is this on a network?

[quoted text clipped - 24 lines]

 

[JamesJ]

My symptons aren't exactly what is described on this HotFix.
Should I install anyway??

James

Here's one: http://support.microsoft.com/kb/960307

Access 2007 sp 1 - Vista Basic sp 1
Where might I go to check on Hotfixes?

James

You also did not mention which version of Access you were using. Have
you
applied all of the Service packs and the HotFixes? Is this on a network?

[quoted text clipped - 24 lines]

James

 

[ruralguy via AccessMonster.com]

Yet and then reboot the PC.

My symptons aren't exactly what is described on this HotFix.
Should I install anyway??

James

Here's one: http://support.microsoft.com/kb/960307

[quoted text clipped - 9 lines]

 

[Klaus-Dieter Gundermann]

Hi James,

I am sorry to say that this behaviour seems to very usual with Access.
You will find lot of threads describing your problem.

Usually a Decompile / Repair / Compact (DRC) will solve the problem,
but I have experienced the more complex your application is,
the more corruptions you will get. Currently I am doing about
5 - 10 DRC cycles a day ( With Office XP on Win XP )