Corruption from Copy/Paste/Delete Label

[Harold]

I am getting the dreaded ... encountered a problem... We are sorry...

This is not speciic to a form. It occurs almost on any form new or old where
I copy and paste a control and then maybe delete the label. I inherited the
mdb (it is 2003) and it may have been touched by 2007.

Does anyone have any clues to the source and resolution, outside of avoiding
copy paste and be very careful deleting labels.

 

[Jerry Whittle]

Create a new .mdb database file. Import all objects from the old database
into it. If something won't import, then it's probably so corrupt that you
need to rebuild it from scratch or find a backup before this started to
happen.

 

[Harold]

Tried that both as a single Import for all objects and separate imports per
objects.
I can make it happen by

1). Creating a NEW form
2). From the field list drag and add a field.
3). Cut the label.
4). TRY to save the New form and bang, the crash with apology.

 

[Clif McIrvin]

In a *NEW* .mdb with one table (could be a linked table to an existing
..mdb) and the single new form?

 

[Jerry Whittle]

In that case there's a good chance that something is wrong with the install
of Office or the OS itself.

What happens if you take a problem database file to another computer? That
would be really telling. If you think that it's the computer, make sure that
it has all the OS and Office patches and service packs installed.

There is the Microsoft Office Application Recovery tool in Office 2003 and
the Microsoft Office Diagnostics in Office 2007.

Otherwise it might be time for a wipe and complete restore. I haven't had
very good luck with uninstalling just Office.

 

[Harold]

Interesting. I created a new mdb and using a local table or even a linked
table (the same table previously used unsuccessfully) it is ok and does not
blow up.

The database in question does blow up on any computer.

What is odd is the default font (when creating a new form) on the mdb that
crashes is Calibri. I was told this is used in Office 2007 which leads me to
wonder if the mdb was opened by 2007 and set something internal to the mdb.

 

[Harold]

Possble Resolution:

I created a new blank mdb. Oddly the Form Template under the Options Tab
says Main_Form which was what I defined in the errant mdb. Somehow Office
must keep this definition because the form does not exist yet. I then began
impoting objects in groups. Everything worked fine until the Form Template
"Main_From" was imported. At that time, on a new form, Calibri began
appearing on my new forms and the cut of the label can force a crash. I went
to Main_Form deleted all objects but as long as it is defined as the From
Template, a new form has Calibri and cutting label blows it up. If I set the
Form Template to Normal life seems okay.

Very, very strange.

 

[Clif McIrvin]

As you say ... interesting.

My development experience is limited (non-existant on 2007) ... I am
pretty certain that Access has settings that are maintained
independantly of any .mdb files that it creates.

From what you say it does sound suspiciously as though the db in
question has been "touched" by A2007.

Is there a backup copy of the front end (this *is* a split db, right?)
that does not have the problem?
If so, simply trash the bad copy and replace it with a *copy* of the
good backup.

Can you (by selectively importing) create a "clone" of the problem
database that does not have the problem?

If this is not a split db, it's time to split it and insure that *every*
user has their own private copy of the front end (FE).

I don't have the references at hand; a Google search for Tony's FE
AutoUpdater will supply you with much valuable information ... and links
to download top-notch free utilities.

Good luck!

Clif