RE: 5 access 2000 users and 1 AccessXP user

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


"Anna S" wrote:

> Hi
>
> I have an Access 2000 database that is used by multiple users. The DB is
> split with the backend on a server.
>
> I have 1 user who wants to use the DB but they have Office XP (Access 2002)
> installed.
>
> I feared that the 2000 users may have trouble using the backend if a 2002
> user accessed it ( I recall having these issues with 97 and 2000).
>
> I tested this theory on a copy of the backend and 2002 seems to be able to
> use the 2000 backend and preserve 2000's ability to access it thereafter.
>
> My problem is that I can get the mdb version of my Access 2000 front end to
> work on the 2002 PC but the mde version created in 2000 will not work.
>
> There is a message about a function or VBA code that Access can't find .
> This is then followed by a message to the effect that the mde is corrupted.
>
> I was not able to create an mde on the 2002 PC without upgrading the
> database to 2002 format. I assume this would mean the back end too - i don't
> want this.
>
> the application uses Word and Excel libraries too. The list of References
> for the 2000 version is shown below
>
> ListReferences
> VBA: C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL
> Access: C:\Program Files\Microsoft Office\Office\MSACC9.OLB
> Word: C:\Program Files\Microsoft Office\Office\MSWORD9.OLB
> MSACAL: C:\WINNT\system32\MSCAL.OCX
> stdole: C:\WINNT\System32\stdole2.tlb
> DAO: C:\Program Files\Common Files\Microsoft Shared\DAO\dao360.dll
> VBIDE: C:\Program Files\Common Files\Microsoft
> Shared\VBA\VBA6\VBE6EXT.OLB
> Office: C:\Program Files\Microsoft Office\Office\MSO9.DLL
> vsFlexLib: C:\WINNT\System32\VSFLEX3.OCX
>
> Does anyone know what I can do to create an mde version for the 2002 pc that
> won't make the backend unusable for the 2000 users?
>
> Any advice gratefully accepted.
>
> Anna
>
>
.

Relevant Pages

  • Re: Access 2000 with SQL Server - MultiUsers
    ... However the drawback is more active connections to the server, ... As far as the backend goes I've run 50 to 200 people updating a MS Access 97 ... then disconnect from the backend. ... Jet doesn't disconnect you from the database ...
    (microsoft.public.access.externaldata)
  • Re: Database design for a network
    ... What's the difference between "the application" and "the frontend"? ... > the server, just one session of access on each individual ... > backend is created per MDE backend module regardless of ... >>> Sooner or later your frontend MDE is going to become ...
    (microsoft.public.access.gettingstarted)
  • Re: Database design for a network
    ... of a power user writing an app for my own small company. ... PCs connected to a server. ... creating an mde version - I think the implication of some of the postings is ... backend is created per MDE backend module regardless of ...
    (microsoft.public.access.gettingstarted)
  • Re: Synchronization Module
    ... The master copy is on my local server. ... So there is no backend at this point because I haven't been able ... to your question is that it is a database that has the data tables ... If you continue to synch your unsplit ...
    (microsoft.public.access.queries)
  • Re: Converting Access 2k to Web
    ... Each 'employee' would have a copy of the front end of the ... TS clients login to the server: ... and open the database front end. ... tap into my server for the backend database. ...
    (microsoft.public.access.forms)