Access 2003 Database corrupted

[Dave]

Every time I try to load my forms I am getting the message:

"Invalid Procedure Call or Argument"

The error is triggered in the Form_Load event. If I remove all code from
this event the error will not occur.

I am experiencing the same error in all forms with Form_Load code.

The code behind these forms has not been touched in several weeks and
everything was working fine up until the other day.

THe only thing unusuall that happened lately was I opened this Access 2003
database on a box that only had Access 2007. The database seem to load fine
but I wonder if somehow it was reconfigured after use in Access 2007.

Does this seem possible? Are there cases reported where Access 2007 trys to
convert 2003 databases when they are opened in 2007?

Any ideas what the problem may be?

 

[Gina Whipp]

Thought... check your references. Might be some stil looking for 2007
libraries. Just uncheck the ones that say MISSING. You MAY have to recheck
the appropiate ones.

--
Gina Whipp

"I feel I have been denied critical, need to know, information!" - Tremors
II

http://www.regina-whipp.com/index.htm

 

[Stephen @ ZennHAUS]

Hey Dave

Yes, this certainly seems possible. I use both Access 2003 and 2007
simultaneously to develop databases because each product has its benefits
especially when the database will be used in Access 2003. However, a recent
(October sometime) update has caused an incompatibility in code between the
two products. I cannot tell you exactly how or why it happens, but it
occurs in databases that have been opened in Access 2007 or on machines that
have both Access 2003 and Access 2007 installed.

The work around that I have found after many hours of unsuccessfully trying
to resolve the issue from a technical standpoint is as follows:

Create a new empty Database in Access 2003 on a machine that has never had
2007 installed on it.

Convert the database to 2003 format

Open VB Editor and ensure all the required references are set up.

Import all the objects from the previous database starting with tables, then
queries, then forms/reports.

If you import all of the tables at once, the relationships will come across.

In one instance I have had to rebuild ALL of my forms from scratch and I
have also found the problem is not limited to just Form_Load(). All of my
previous projects that were created the same way and have worked
successfully in both products till now have the same issue and no longer
work.

If you need to use this on both products at the same time (ie. some clients
in 2003 and some in 2007), create the entire database in Access 2003, split
it using 2003, duplicate the 2003 interface and make the copy for use in
2007 only. That way you will have a working interface for 2003 (the original
and ongoing developmental interface) and one for 2007.

Not a particularly technical workaround, but it does work.

Cheers

Stephen @ ZennHAUS