Re: 5 access 2000 users and 1 AccessXP user

Allen:

Making the user an administrator on the local machine worked for the case
where I upgraded a win2K box to winXP and kept Office 2000 untouched (the
Access database in question is in Access 2000). Thank you very much.

However, for the case where I brought in a new, out of the box, PC with Win
XP and Office 2003 pre-loaded, I cannot get the front end to open once I copy
it to th PC (it is an mde file). I get all kinds of errors (not read-only
errors like the win2K box). The back end is on a server running win2K server.

Can you help regarding this remaining problem by giving me any other
suggestions? I am very happy to have the problem solved on the win2K box so
we can at least use our application.
--
BZ - Essex, Massachusetts, USA


"Allen Browne" wrote:

> Suggestions:
>
> 1. Using Windows Explorer, locate the front end mdb file on the workstation.
> Right-click and choose Properties. Make sure the Read-Only check box is
> unchecked. If you see an Unblock button, click that. (Typically where the
> file was received by email.)
>
> 2. Go to Tools | Options on each of the Access workstations, and set:
> Advanced | Default Open Mode to "Shared".
> General | Name AutoCorrect boxes to unchecked.
>
> 3. Make sure Sandbox mode is disabled:
> http://support.microsoft.com/kb/239482/en-us
>
> 4. Check the permissions of the folder where the workstations are connected
> to. They need read, write, and delete permissions. (I have one client whose
> "server" has multiple hierarchial shares on the drive, and if they choose
> the wrong one (a top-level read-only) instead of the lower-level
> write-enabled share, they get this problem.)
>
> 5. Make sure the users are logged in as local-computer administrators (not
> limited users.)
>
> 6. Make sure all users have Service Pack 8 for JET 4. Locate the file
> msjet40.dll. Right-click and choose Properties. On the Version tab, you
> should see 40.8xxx.0. The xxx digits don't matter, but if you don't see the
> 8, download from:
> http://support.microsoft.com/kb/239114
>
> 7. If the problem still persists, the "read-only" message can occur because
> *one* of the workstations has opened the data exclusively.
>
> --
> Allen Browne - Microsoft MVP. Perth, Western Australia.
> Tips for Access users - http://allenbrowne.com/tips.html
> Reply to group, rather than allenbrowne at mvps dot org.
>
> "Brendhan" <Brendhan@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:DB274A77-FAD4-4524-B45B-FE2528A5FEAE@xxxxxxxxxxxxxxxx
> > Anna:
> >
> > I have a question that perhaps you or someone else in the group can
> > answer.
> > I, too, have a split database with the backend on a server. I recently
> > started upgrading my win2K clients to XP and the server is still running
> > win2K Server. I tried to open the database using Access 2000 on one of
> > the
> > clients that I upgraded to XP and I get a message indicating that the
> > database is read only (which isn't true) and, although I can see the data,
> > the program won't let me change anything.
> >
> > Also, I have some brand-new XP clients that came with Access 2003
> > pre-loaded. These can't even open the database - even as read only. The
> > problem obviously has something to do with a Windows 2000 server and a win
> > XP
> > client with respect to Access 2000.
> >
> > Can anyone help?
> > --
> > BZ
>
>
>
.