Access working slowly on a network

[Guest]

I use a Access 2K mdb on a server based network running Server 2003. Six
standalone workstations link to individual front ends and share data tables
on the back end. All files are on the server with the PCs linked via
shortcuts. At times the database struggles to open various forms and
reports. Would putting the front ends on each PC help speed things up? All
PCs (each running XP Pro) and the server are new and very fast machines. Any
suggestions to speed things up would be greatly appreciated. One other
possible issue...the version of Access 2000 running everything has not had
any patches or updates applied. Should that be updated?

 

[(PeteCresswell)]

Per DMainland:

Would putting the front ends on each PC help speed things up?

Dunno how much it would speed things up but it has to help.

Also, if you have multi users concurrently executing the same
front end, I'd think you're headed for trouble anyway.

The Good-Right-And-Holy-Path as I know it involves each user
executing their own copy of the front end - preferably from their
own PC.

 

[Joseph Meehan]

I use a Access 2K mdb on a server based network running Server 2003.
Six standalone workstations link to individual front ends and share
data tables on the back end. All files are on the server with the
PCs linked via shortcuts. At times the database struggles to open
various forms and reports. Would putting the front ends on each PC
help speed things up? All PCs (each running XP Pro) and the server
are new and very fast machines. Any suggestions to speed things up
would be greatly appreciated. One other possible issue...the version
of Access 2000 running everything has not had any patches or updates
applied. Should that be updated?

I would start by putting all the front ends on the individuals PC. That
will help a lot and that is the way it is designed to work. Assuming that
you have a good solid LAN that should take care of your problem.

 

[John W. Vinson]

.the version of Access 2000 running everything has not had
any patches or updates applied. Should that be updated?

<GAG> <sputter>

Yes. That's a bit like saying "My auto dealer has sent out 18 safety
bulletins, should I take my car in?"

A2000 as released was VERY buggy - not quite as bad as the infamous A95 but it
had LOTS of problems.

By all means, split the app so each user has their own copy of the frontend,
on their own machine, and apply all the A2000 patches and updates. Don't
dawdle on this! You're on thin ice currently!

See http://www.granite.ab.ca/access/splitapp/ for Tony's review of the best
practices for this situation. You'll want to (for instance) have a recordset
open persistantly (say from the frontend's startup form) to ensure better
performance.

John W. Vinson [MVP]

 

[dbahooker]

you're full of crap kid

move to SQL Server and Access Data Projects

MDB isn't reliable enough for real world usage


]

 

[dbahooker]

a 'good solid lan'

these dipshits around here always try to blame stuff on the network..
it's hilarious

it's called 'PASSING THE BUCK'

You dipshits need to stop blaming others and start using a real
database-- like SQL Server for example

 

[dbahooker]

and for the record?

If you're not using OfficeUpdate.Microsoft.com then you're just asking
for trouble

and Access 2000 is the worst edition in the past 5 releases
so yeah

upgrade to a new version of Access like 2002 or 2003; and always run
patches on all your machines
I mean are you stupid or something?

retarded?

of course you should always run all the patches; get over it; it's not
that big of a deal

 

[Joseph Meehan]

a 'good solid lan'

these dipshits around here always try to blame stuff on the network..
it's hilarious

it's called 'PASSING THE BUCK'

You dipshits need to stop blaming others and start using a real
database-- like SQL Server for example

Sorry about Aaron - you get all types in a public forum!!