what is

Topic

New Reply

what is

Reply | Quote

Replies

Arage,

Maybe this can be of some help

Reply | Quote

that worked!

Reply | Quote

I am receiving this error now on those user machines that have been upgraded to Windows 2000 when attempting to access Access97 databases that reside on a Banyan network drive. We are making the move to a Windows 2000 network system, so this is not a big problem, but it is an irritation none-the-less. Does anyone have any ideas as to why this is happening or what can be done to correct it?
thx,
Pat Williams

Reply | Quote

I believe your problem stems from not pointing to the Access97 System.MDW file for security purposes. Check and see if you are pointing to an Access 2000 version of the file which by default is in folder
C:Program FilesMicrosoft OfficeOffice
Search for another security file to find the Access97 one, and then use the Workgroup Administrator to point to that file and see if that solves your problem. Aren’t upgrades fun?

Reply | Quote

Hi, Wendell,
Oh, yeah, upgrades are fun!
Thanks for your reply, I tried what you suggested — in a way. I am using Access 97 on a Win 2000 machine, and my system.mdw is in C:WINNTSYSTEM32system.mdw. Anyway, I joined the (still plain vanilla system.mdw, no changes at all) workgroup that I had placed on the network along with the install that I had created earlier (while still under a Win95/98 system), figuring that I would at least be pointing back to the original. I still failed w/ the same error.
It happens just like this w/ more than one database and more than one Win2000 desktop, just to add that it’s not just one particular database or desktop that’s giving the trouble.
And, come to think of it (don’t know why I didn’t think of this first), if I access a database where the (Access 97 db) front end is on c: but which links to a data backend (Access97 db) on a Banyan drive, it works fine — so it probably isn’t the system.mdw.
So, still perplexed, although I could move the databases or split them all, so it’s not an eventual biggie, just an inconvenience and extra work up front, but, still …. it’s annoying.
Anyway, thanks again for the reply, it was worth a shot!
Pat

| I believe your problem stems from not pointing to the
| Access97 System.MDW file for security purposes. Check and
| see if you are pointing to an Access 2000 version of the
| file which by default is in folder
| C:Program FilesMicrosoft OfficeOffice
| Search for another security file to find the Access97 one,
| and then use the Workgroup Administrator to point to that
| file and see if that solves your problem. Aren’t upgrades
| fun? (sigh)
|
| Wendell Bell (gramps)
| Access-Experts.com

Reply | Quote

Oops! I misread your post – I thought you were upgrading from Access 97 to Access 2000.

There are some sticky issues in running Access 97 apps on Win2000 desktops. We finally bit the bullet at a large client and upgraded to Office 2K because of stability problems we were having with Access 97 databases when we began upgrading to Win2000. It seems to me that there was an issue with Windows 2000 Pro that was fixed in a Service Pack and things got better, but I haven’t been able to locate anything about it this morning. Does the process described in the KB article posted by Francois solve your problem? And are you dealing with MDE files or MDB files? You indicate it’s a pain, but only a minor one so I assume you have found a solution that takes some effort. Sorry for the confusion.

Reply | Quote