3
Hello -
This is my first posting to this group, so please bear with me. Also note, that while I'm intelligent, databases are not in my field of knowledge.
I'm working with a small limousine company. They presently have about 4 networked computers, all running Windows XP (w/SP2) and Microsoft Office 2000 (specifically Access 2000) - and a plain jane p3 server also running Windows XP (w/sp2) with Office 2000 loaded onto it.
These networked computers are accessing an Access 2000 .mdb file, in a multi-user fashion (more then one user is accessing this shared file at any given time) from the above mentioned server. This file is their customer database, used to run their business.
It should be noted, that this customers MUST use Access 2000, as using Access XP (2002 ?) as above causes the database to do weird things, such as create blank records, or input records that are non –contiguous. At one time, an Access database guru told me why Access XP (2002) does this, but I cannot recall the details - plus it was some time ago.
Moving forward -
This company recently purchased 4 new Dell E520's (Dual Core P4's) with the new lovely (smirk) Windows Vista 32 bit Business OS preinstalled on them.
I have installed these 4 new Dell E520 systems and networked them with the above mentioned server. All the normal stuff is working, Internet , etc etc.
I then installed (don't laugh or joke) Office 2000, just to check things out.
Now - they are no longer able to launch the Access database file (that lives on the above mentioned server), in a multi-user fashion any longer.
Example: if one user opens the file, no other networked users can open the file on the server. When the second or subsequent user double clicks the Alias to launch the database file, Vista's little blue ring goes around a few times, but nothing ever happens.
if user one exits the file, then the next subsequent user can then open the database file, but the next subsequent user cannot. so on and so forth.
Your saying to yourself - well duh - upgrade it to a newer version of Acess right? - even though it has some issues (as identified above).
Yes - I did that. I then installed and tested with Office XP (2002), Office 2003 (w/SP2), and lastly, Office 2007.
All yielded the same results, I cannot run the file in a muli-users fashion, as before in the XP environment.
I tried setting the msaccess compatibility mode to both Windows XP SP2 and Windows 2000 (for each verion of the Office apps above) - still no luck.
I tried seeting msaccess to run in Admin mode (on all above versions) - no luck
I tried Admin mode & the above compatibility mode options together - no luck.
I tried updating the access 2000 .mdb database file to the Access 2003 format using the Access 2003 conversion tool, and attempted to perform all the above testing routine again - even with Office 2007 - Still no multi-user support.
At this point - I'm at a loss to get this to work, so I have come here seeking guidance, answers, help, etc etc.
Can anyone offer me some input as to why I'm unable to run this file in a multi-user fashion under Vista and (pick your version of Office), as I used to be able to do in the XP enviroment ?
Any assistance would be greatly appreciated.
Thanks
Leonard
