Office xp access issue

[Auger282]

I'm having a slight issue with one of my machines when we are upgrading from office 2000 to office xp. I have a database that gets auto updated from a version out on the network. From one machine it works fine but on this other one we are getting an error.

Abort Operation
Error 5 recieved while attempting to verify database version.
Invalid procedure call or argument.

Please ensure that the shortcut that starts this program contains '/cmd' followed by the network directory (enclosed with quotes) of the new .mde file to be checked.



Shortcut Target:

"C:\Program Files\Microsoft Office\Office10\MSACCESS.EXE" "C:\OEE\DBUpdate.mde" /runtime /cmd "O:\Shared\OEE\Install\"


the shortcut and the files on the local machines are exactly the same... I've tried reinstalling.. both Offices have all the latest updates and service packs.

any ideas?

 

[mp9]

Just to rule out the obviouos - both users/PCs have their O drive mapped to the same place?

 

[JockMullin]

Bit of a shot in the dark, but error 5 usually means access denied (sharing violation). Are you sure the shared resources are not locked - check the status of the shares on the server - maybe another task has them exclusively.

Try again when no users have the shares open.

Jock

 

[JockMullin]

Hi, again, pressed Submit too soon ...

Alternatively it could be a rights issue - does the user have the same rights to the shares as the other users?

Jock

 

[Auger282]

Well .. its not a mapping or a rights issue..

I've tested it on machines with admin rights and with min. All the computers here have the O drive mapping.

I'm wondering if there isnt something installed on the problem machines that I have on mine and the other ones that work in my testing lab (that all work fine).

I'm guessing there is some vb in the database for coding .. but I do have the VB stuff installing by default in the mst.

Thanks for the ideas.. I'm willing to entertain more if you guys come up with any!

 

[Auger282]

I did find out what the issue was.
There was a const setup within the update database that pointed directly to the access directory.

This poses a problem because office is in a different directory for 2000 and xp.

The older is in
c:\program files\microsoft office\office\

and the new in
c:\program files\microsoft office\office10\

I have since resolved the issue by creating a second database for use with our office XP clients.

Thanks for all your help!