Access 2000 Crash & Burn

[JC3]

Hi

I have a DB which has been up and running with no problems for a couple of months.

A couple of users have recently had new machines installed. These are XP SP2 with Office 2000.

The Database FE is on the PC and the Backend is on the server.

When FE is first downloaded and opened it runs fine. The second time you go in the DB gets by the Splash screen but then crashes on the Title Menu. If you then recopy the FE to the machine it opens fine the first time then crashes again on the second attempt.

I have checked the references and all ok. I have full error trapping on the Splash screen and the Title Menu yet I just get the error "Access has encountered an error and needs to close..."

It runs fine on my machine which is XP SP2 with Office 2002. Has anyone any suggestions that I can check or repair this?

JC

 

[ghudson]

What version of access is the db in for the two users with the problem? You state they have Office 2000 yet you are using Office 2002. Did you down save the db to Access 2000 for those two users? Have you opened the db on their PCs [bypassed your startup stuff] and compiled the db to see if there are any code errors or missing references? Missing references and the use of furture functions that the down graded db does not recognize are common problems when working with different Versions of Access.

 

[JC3]

The DB was and Access 2000 version originally created using 2002. I have tried to compile the DB and check for references and no errors. This wouldn't explain why it works fine the first time you go into it and not the second time. Is it possible that it is leaving some remnant in memory which is affecting it on the second attempt or it is corrupting the DB when it is used the first time.

If so any ideas how I would check these to see?

JC

 

[JC3]

Hi all

I have done some testing with the /decompile switch and when this is added to the DB shortcut the DB appears to run fine (slower obviously but no crashes).

From everything I have read about Decompile people advise not to use it regularly. If this is true is there a way to programatically decompile and then recompile the FE when it is downloaded to the users machine so it compiles correctly for their version.

Currently I do a check of the version when it loads and if it requires an update the db calls a batch file which closes the DB, copies the correct FE across and then reopens the db. I could obviously use the /Decompile switch when I copy it over but is there a way to Compile the DB short of going into the VBA editor and Compiling?

I initially thought that once it was decompiled then it would recompile as an when you used each module but as soon as I removed the /Decompile switch from the Shortcut the problem reoccurred.

JC

 

[neileg]

You need to compile and check for references on the machines that have the problem, not on your own machine. Have you done that?

 

[JC3]

My machine has been fine therefore understandably all my testing has been on the users machine to try and identify the problem.

I would also advise

a) The DB's worked fine up until a week or two ago. There have been no major changes since then.

b) Another DB is also showing exactly the same problem on a different DB. They are also using Access 2000.

The only significant change in the last couple of week is the machines have updated with the XP SP2 update. I can't find any mention of a known problem with Access 2000 in relation to this.

Any ideas?

 

[ghudson]

The only significant change in the last couple of week is the machines have updated with the XP SP2 update. I can't find any mention of a known problem with Access 2000 in relation to this.

Sounds like you have identified your problem. Have you tried reinstalling Office? Why not ugrade everybody to Office 2002 [if that is the highest version your company has]?

 

[JC3]

Thans Everyone.

I will try the re-install and if that doesn't work I'll see if I can convince them to pay for an upgrade for Access 2000 users (I can always hope).

Thanks again.

JC

 

[neileg]

SP2 has a reputation for causing problems with all sorts of systems. I don't think Access is exempt from this. Machines with XP that have had SP2 from a clean install seem to have fewer problems, and machines that have a version of XP that incorporates all of the SP2 improvements from scratch seem to have very few issues.