Re: Incompatibility between Access 2003 and Access 2002

It is specific to the database in question. I have several others that work
fine on both computers.

"Allen Browne" wrote:

Try opening another database, such as Northwind.
Does that crash also as soon as you open a code window?

We are trying to determine whether this is specific to the database
(suggesting a corruption or bad reference) or to the computer (suggesting a
corrupted installation of Access, a faulty add-in, or interference from a
..NET version of VB.)

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"vp17tacco" <vp17tacco@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B3EB1B4D-CF36-4FC2-BF02-2623EDAF20C4@xxxxxxxxxxxxxxxx
Thank you for your reply. There is no AutoExec macro. Holding the shift
key
down during startup does delay the crash and, while still holding the
shift
key down, I can even open the startup form in design view, but when I
release
the shift key, the crash occurs. I've also tried opening the code window
while holding the shift key down. This causes the crash to occur
immediately. I don't think the problem is in the startup form. I haven't
made any changes to it recently and I've removed it from the Options menu
as
the startup form, so it doesn't run during startup anymore.

"Allen Browne" wrote:

Firstly, make sure Name AutoCorrect is off. Explanation:
http://allenbrowne.com/bug-03.html

The file format won't make a difference. The Decompile is a good idea
whenever you switch version, as the binaries are different. After the
decompile, make sure *no* code runs (e.g. not even startup code), and
compact the database (again not running any code when if it restarts.)

At what point does it crash? When you open the database? Open a
particular
form? Execute a particular query? Open the code window?

What libraries are you using? (Tools | References from the code window)?

What service packs are applied?

"vp17tacco" <vp17tacco@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:22CC431C-B38E-4FD6-9FC7-3B91E7DD8683@xxxxxxxxxxxxxxxx
I have been writing an Access application using two computers, one of
which
runs Access 2002 and the other Access 2003. Ever since the project
began
I've been able to copy the mdb file (formatted for Access 2000) back
and
forth with no problem. Recently, however, after making some changes on
the
Access 2002 computer, running the file on the Access 2003 computer
causes
a
"Microsoft Access has encountered a problem and needs to close." error.
I've
tried the following: changing the format to Access 2002 (no help),
decompiling the file in Access 2002 (no help), running the file on
other
computers loaded with Access 2003 (same problem). All the while, it
continues to run fine on the Access 2002 machine. Can anyone help me
with
this?



.

Relevant Pages

  • Re: Incompatibility between Access 2003 and Access 2002
    ... Try opening another database, such as Northwind. ... Does that crash also as soon as you open a code window? ... I don't think the problem is in the startup form. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Incompatibility between Access 2003 and Access 2002
    ... let's work on the assumption that this is a corruption this database. ... Remember to hold down shift if it restarts. ... Does that crash also as soon as you open a code window? ... I don't think the problem is in the startup form. ...
    (microsoft.public.access.modulesdaovba)
  • lots of noble deaths are elderly and other gorgeous contractors are circular, but will Gul halt that
    ... If you will lack Clifford's market behind ventures, ... crash the will. ... The handling due to the long database is the ...
    (sci.crypt)
  • Re: Code window Crashes!
    ... I wouldn't expect a crash from this, but do you have a form open that has a timer event running? ... everytime the timer event is tripped the focus moves from the VBA window to the open form. ... First experiment is to try to launch your database while holding down the shift key. ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Help: hard drive issue
    ... the strange thing is every night during database refresh, ... The O/S SHOULD NEVER CRASH!!! ... If you have a Sun support contract, you should be getting in touch with ...
    (comp.sys.sun.admin)
Loading