If the application runs fine in local mode (that is, the database is fast
when accessed from the same PC it resides on) but slow over the network,
it's almost surely the network that's to blame for the slowdown.
Unfortunately, knowing where the blame lies doesn't mean it can be resolved.
Accessing data over the network will always be slower than accessing the
same data over a local hard drive. That's because a network's top speed is
slower than a hard drive's top speed by a factor of several hundred times.
An operation that takes a tiny fraction of a second locally may well take
several seconds when run over a network. And accessing a database, where
the data may be accessed dozens or hundreds of times ... well, I think
you're getting the picture here.
--
Richard G. Harper ((E-Mail Removed)) MVP Win9x
* Please post all messages and replies in the newsgroup so that
* all may benefit. Private mail is usually not replied to.
* Help US Help YOU ...
http://www.dts-l.org/goodpost.htm
"chas" <(E-Mail Removed)> wrote in message
news:05b201c3ab67$68bf6220$(E-Mail Removed)...
> We have recently installed a 20 user system at our site.
> This has been done with an outsourced local company, but
> the software comes from another source. The software is
> basically and ACCESS database, and utilises Jetstream
> software for the administration or so i am lead to
> believe! We have windows 98 terminals and an NT server.
> The problem is that the network providers often blame the
> speed of the data access and storage on the software house
> and the software house blame the network. No matter how
> often we have got the two together we have not yet
> resolved the speed of the system.
>
> Does anyone have any information regarding the max size of
> an ACCESS database and if this has an effect on speed (our
> database is approx 21000 cilents) / OR are there any
> compatibility problems running NT and 98 side by side that
> anyone has experienced.
>
> I hope someone can help. Thanks