We have an access application which is kept on a server and user access this
application from his desktop. It is really slow when users are trying to
access it. The users are having Windows XP OS on thier machine. This problem
started when the users migrated to XP environment.
Please help me

The application should be on their desktop, not on the server.

If this is a shared application, then it should be split into a front-end
(containing the queries, forms, reports, macros and modules) linked to a
back-end (containing the tables). The back-end should be on the server, and
each user should have his/her own copy of the front end on their desktop.

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(No private e-mails, please)


"Gautham" <(E-Mail Removed)> wrote in message
news:94D25633-408A-4521-90C0-(E-Mail Removed)...
> We have an access application which is kept on a server and user access
this
> application from his desktop. It is really slow when users are trying to
> access it. The users are having Windows XP OS on thier machine. This
problem
> started when the users migrated to XP environment.
> Please help me

what does this have to do with XP ? I'm running a multi-user db in WIN2000
and it works fine. Not super speedy, but fast enough. I tried to split it in
front and back once but it slowed down enormously. It probably has to do with
how forms were created, but I didn't feel like recreating the whole db.
The way I see it is that currently the whole db is taken from the server to
the client when opening. Once opened, the data is on the client so when the
forms are opened, the data doesn't have to be reloaded. When the tables are
on the server, every time you open up a form, all data needs to be refreshed
from the server.
I'm just asking here because I 'm curious in case we are ever upgrade to XP.

"Douglas J. Steele" wrote:

> The application should be on their desktop, not on the server.
>
> If this is a shared application, then it should be split into a front-end
> (containing the queries, forms, reports, macros and modules) linked to a
> back-end (containing the tables). The back-end should be on the server, and
> each user should have his/her own copy of the front end on their desktop.
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (No private e-mails, please)
>
>
> "Gautham" <(E-Mail Removed)> wrote in message
> news:94D25633-408A-4521-90C0-(E-Mail Removed)...
> > We have an access application which is kept on a server and user access
> this
> > application from his desktop. It is really slow when users are trying to
> > access it. The users are having Windows XP OS on thier machine. This
> problem
> > started when the users migrated to XP environment.
> > Please help me
>
>
>

Hi,
We have a front end and backend both kept on the network server and user
have a shortcut to the launch the FE. FE has linked tables, which are linked
to the BE Access Db. When the users were on NT this was quite faster and
there was no issues. When the users moved on to XP 2-3 weeks ago we migrated
all the access 97 applications to MS Access 2002. Now they are experiencing
the problem with speed.
We have also tried creating MDE and copying it to the users machine. even
that didn't make any difference.

"nova" wrote:

> what does this have to do with XP ? I'm running a multi-user db in WIN2000
> and it works fine. Not super speedy, but fast enough. I tried to split it in
> front and back once but it slowed down enormously. It probably has to do with
> how forms were created, but I didn't feel like recreating the whole db.
> The way I see it is that currently the whole db is taken from the server to
> the client when opening. Once opened, the data is on the client so when the
> forms are opened, the data doesn't have to be reloaded. When the tables are
> on the server, every time you open up a form, all data needs to be refreshed
> from the server.
> I'm just asking here because I 'm curious in case we are ever upgrade to XP.
>
> "Douglas J. Steele" wrote:
>
> > The application should be on their desktop, not on the server.
> >
> > If this is a shared application, then it should be split into a front-end
> > (containing the queries, forms, reports, macros and modules) linked to a
> > back-end (containing the tables). The back-end should be on the server, and
> > each user should have his/her own copy of the front end on their desktop.
> >
> > --
> > Doug Steele, Microsoft Access MVP
> > http://I.Am/DougSteele
> > (No private e-mails, please)
> >
> >
> > "Gautham" <(E-Mail Removed)> wrote in message
> > news:94D25633-408A-4521-90C0-(E-Mail Removed)...
> > > We have an access application which is kept on a server and user access
> > this
> > > application from his desktop. It is really slow when users are trying to
> > > access it. The users are having Windows XP OS on thier machine. This
> > problem
> > > started when the users migrated to XP environment.
> > > Please help me
> >
> >
> >