Runtime errors when using Access 2000 alongside XP (Access 2000 & Access X

Topic

New Reply

I have a problem with an Access database that is being accessed multi-user by Office 2000 users and Office XP users simultaneously. If only Access 2000 users use it, everything is fine. When an Access XP (office XP) user uses it, they can login and out fine for the first time, but on second or subsequent logins at all goes horribly wrong. Office XP users start getting a range of Runtime Errors (often relating to fields not being allowed to be zero length, when the data is there and even if it wasn’t it could allow zero length and Runtime Error 91 – Object Variable or with Block Variable not set is also quite popular). Access 2000 users will then also start to get Runtime errors. These runtime errors cause Access to shutdown on XP, but clicking on the End button on an Access 2000 workstation allows the users to continue working as usual.
Compacting and repairing the database gets rid of the Runtime Errors altogether, but as soon as an Office XP user starts using the database it all starts to happen again.
We’ve tried creating a new database and importing all of the forms, tables, etc. This only temporarily clears the problem and offers no better fix than compacting and repairing.
I thought that you could use an Access 2000 format database with both Office 2000 and Office XP (if it is not converted to Access XP format, or whatever it’s called) but I am starting to wonder if that is the case.
Has anyone experienced a similar problem or can anyone offer any advice?

Thanks in anticipation!

Reply | Quote

Replies

I don’t have an explanation, but consider splitting the database into a backend (containing only the tables) and frontends (containing all other database objects, plus links to the tables in the backend.) Create separate frontends for Access 2000 and Access 2002; both can be in Access 2000 format, but compile the code (Debug | Compile in the Visual Basic Editor) for each in the target application. It is best to give each user a local copy of the frontend suitable for his/her Access version.

Reply | Quote

Thank you Hans
I got so bogged down in it all I didn’t even think of that. I may even get some performance improvements from it too. I’ll give it a go and post the results here.

Regards
Tony

Reply | Quote

Thank you Hans
I got so bogged down in it all I didn’t even think of that. I may even get some performance improvements from it too. I’ll give it a go and post the results here.

Regards
Tony

Reply | Quote

This is a follow-on from problem discussed between tdakc, HansV and charlotte on 25/05/04. Having problems with a front-end database being used solely by Access 2000 users. The database is reporting run-time error 2448 (Can’t assign a value to this object) at various stages, in similar style to the run-time errors previously reported by tdakc. We have checked the version of MS Jet 4.0 on all PCs and they are all on different Service Packs, ranging from SP3 to SP 6. The Windows versions used are also different – 98, 2000 and XP. Has anyone else experienced similar problems with users on the same version of Access, but differing Jet Service Packs and did installing the latest Service Pack (8) solve the problem? You assistance would be gratefully received.

Reply | Quote

The “same” version of Access is NOT the same if they are using different Jet service packs. It has nothing to do with the version of Windows and everything to do with the Jet engine, which is at the heart of Access. I would suggest you start a new thread on the specific questions you have. Runtime errors that are similar in style to this discussion doesn’t provide specific enough information for us to be of help.

Reply | Quote

Thanks for your response Charlotte.

Reply | Quote

Thanks for your response Charlotte.

Reply | Quote

The “same” version of Access is NOT the same if they are using different Jet service packs. It has nothing to do with the version of Windows and everything to do with the Jet engine, which is at the heart of Access. I would suggest you start a new thread on the specific questions you have. Runtime errors that are similar in style to this discussion doesn’t provide specific enough information for us to be of help.

Reply | Quote

This is a follow-on from problem discussed between tdakc, HansV and charlotte on 25/05/04. Having problems with a front-end database being used solely by Access 2000 users. The database is reporting run-time error 2448 (Can’t assign a value to this object) at various stages, in similar style to the run-time errors previously reported by tdakc. We have checked the version of MS Jet 4.0 on all PCs and they are all on different Service Packs, ranging from SP3 to SP 6. The Windows versions used are also different – 98, 2000 and XP. Has anyone else experienced similar problems with users on the same version of Access, but differing Jet Service Packs and did installing the latest Service Pack (8) solve the problem? You assistance would be gratefully received.

Reply | Quote

Are all the machines at the same Jet service pack? Are all the machines patched to the latest Office service packs? Office 2000 and XP install different versions of the VBE6.DLL, which can cause weird problems in 2000. Differences in Jet service packs can drive you crazy too. I routinely open 2000 format files in either 2000 or XP, whichever I think of first, without problems. However, from your later post, it appears that this database may be on a shared drive, with everyone accessing the same application file from different versions at the same time. That is bound to cause problems because of the slight differences between the versions and I heartily endorse Hans’ suggestion of splitting the database immediately.

Reply | Quote

Thanks Charlotte,
They did have all the latest service packs when I check about a month ago, but I suppose that doesn’t mean they haven’t reinstalled since. I’ll double check the Service Pack levels for Office and Jet when I split the databases tomorrow morning.
Thanks again.

Tony

Reply | Quote

Fixed it! Splitting the database, ensuring that all were on the same Jet level and ensuring the code was compliled did the trick.
Thanks very much to HansV and Charlotte for their assistance.

Reply | Quote

Fixed it! Splitting the database, ensuring that all were on the same Jet level and ensuring the code was compliled did the trick.
Thanks very much to HansV and Charlotte for their assistance.

Reply | Quote

Thanks Charlotte,
They did have all the latest service packs when I check about a month ago, but I suppose that doesn’t mean they haven’t reinstalled since. I’ll double check the Service Pack levels for Office and Jet when I split the databases tomorrow morning.
Thanks again.

Tony

Reply | Quote

Are all the machines at the same Jet service pack? Are all the machines patched to the latest Office service packs? Office 2000 and XP install different versions of the VBE6.DLL, which can cause weird problems in 2000. Differences in Jet service packs can drive you crazy too. I routinely open 2000 format files in either 2000 or XP, whichever I think of first, without problems. However, from your later post, it appears that this database may be on a shared drive, with everyone accessing the same application file from different versions at the same time. That is bound to cause problems because of the slight differences between the versions and I heartily endorse Hans’ suggestion of splitting the database immediately.

Reply | Quote