Access has encountered a problem

[Rene T]

I have a database that is used by several companies using different office
versions/networking, etc. I recently did an update that added a field and
changed the way some things were calculated - pretty straight forward stuff.
When I install this update on versions prior to Access 2007, I run into the
dreaded "microsoft Access has encountered a problem..." about 30% of the
time. I thought the problem was because I created an "install database" on
my computer (Access 2007) then imported all the elements into the companys'
front end (Previous versions). I scheduled an update today on a computer and
decided to do it all from scratch using the earlier version with their front
end that has been working properly. Everything was going well until I tried
to add a field to a form. After searching this forum, I read that using
reserved names can cause a problem and I'm wondering if that's what I've
done. The field is called EntryFeeOR (currency format). Can this be the
problem or am I missing something? I can't believe all these versions can be
corrupted and it only happens on earlier versions of Access some of the time.
Any other ideas?

Thanks!

 

[Arvin Meyer [MVP]]

I have a database that is used by several companies using different office
versions/networking, etc. I recently did an update that added a field and
changed the way some things were calculated - pretty straight forward
stuff.
When I install this update on versions prior to Access 2007, I run into
the
dreaded "microsoft Access has encountered a problem..." about 30% of the
time. I thought the problem was because I created an "install database"
on
my computer (Access 2007) then imported all the elements into the
companys'
front end (Previous versions). I scheduled an update today on a computer
and
decided to do it all from scratch using the earlier version with their
front
end that has been working properly. Everything was going well until I
tried
to add a field to a form. After searching this forum, I read that using
reserved names can cause a problem and I'm wondering if that's what I've
done. The field is called EntryFeeOR (currency format). Can this be the
problem or am I missing something? I can't believe all these versions can
be
corrupted and it only happens on earlier versions of Access some of the
time.
Any other ideas?

I think you may be dealing with a corruption problem. A form can corrupt, or
even a single control on that form can corrupt. There are several things to
do:

First, always work on a copy of the database. Working on the original may
make it impossible for a repair service to fix it.

Decompile your database:
http://www.trigeminal.com/usenet/usenet004.asp

Download a copy of JetComp.exe:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;273956

Try backing up your forms as text with the undocumented SaveAsText
LoadFromText functions:

http://www.datastrat.com/Code/DocDatabase.txt

Also have a look at the Microsoft KB article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;209137

Then have a look at Tony Toews' Access Corruption FAQ at:

http://www.granite.ab.ca/access/corruptmdbs.htm

for some suggestions. Unfortunately, some corruption cannot be fixed - you
may need to create a new database, import what can be salvaged, and recreate
the rest.

Although it's a paid service, Peter Miller does an outstanding job of saving
corrupt databases. Try this URL:

http://www.pksolutions.com

--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

Disclaimer: Any code or opinions are offered here as is. Some of that
code has been well tested for number of years. Some of it is untested
"aircode" typed directly into the post. Some may be code from other
authors. Some of the products recommended have been purchased and
used by the author. Others have been furnished by their manufacturers.
Still others have not been personally tested, but have been
recommended by others whom this author respects.