refresh records faster on network

[mcnews]

is there any way to make new records appear any faster?
i have 3 laptops networked to a 4th.
all are using a copy of a front-end mdb locally and are linked to the
back-end mdb that lives on the 4th.
users a re complaining that they don't see new records right away and
in fact don't see them till the restart the mdb.
any way to remedy this?
tia,
mcnewsxp

 

[Guest]

Put the BE on a network server instead of a laptop. I'm guessing that this is
a peer-to-peer network and they can be slow.

Also Access does NOT play well with wireless. I would not trust it to work
right if any of the laptops were connecting to the BE through a wireless
connection.

It could also just be a refreshing issue. If you open and close the form
(without shutting down Access), do the records appear?

Speaking of which, you are viewing the records through forms and reports and
NOT directly though tables and queries, aren't you? There could be some
locking issues othewise.

All users of the database must have at least read, write, and modify
privileges to the folder holding the database file. Not just the database
..mdb file, but the entire folder.

Open the database and go to Tools, Options, and Advanced Tab. Set the
Default Open mode to Shared and the Default Record Locking to Edited Record.
(While you are in the Options area, go over to the General tab and turn off
Compact on Close and Name AutoCorrect. Trust me on this.)

 

[mcnews]

Put the BE on a network server instead of a laptop. I'm guessing that this is

a peer-to-peer network and they can be slow.

not an option because this setup will be used in remote locations.
it needs to be mobile.

Also Access does NOT play well with wireless. I would not trust it to work
right if any of the laptops were connecting to the BE through a wireless
connection.

using a hub.

It could also just be a refreshing issue. If you open and close the form
(without shutting down Access), do the records appear?

yes they do.

Speaking of which, you are viewing the records through forms and reports and
NOT directly though tables and queries, aren't you? There could be some
locking issues othewise.

forms only

All users of the database must have at least read, write, and modify
privileges to the folder holding the database file. Not just the database
.mdb file, but the entire folder.
yep

Open the database and go to Tools, Options, and Advanced Tab. Set the
Default Open mode to Shared and the Default Record Locking to Edited Record.
(While you are in the Options area, go over to the General tab and turn off
Compact on Close and Name AutoCorrect. Trust me on this.)

they are turned off (never turned on).
can you explain why.
again, each user has his own copy of the front-end on their laptop.

 

[Guest]

Also, your program should access the minimum number of records and the
minimum amount of data that it needs. Its usually best to have a design that
accesses only one record at a time rather than reading in a list of records.

-Dorian

 

[mcnews]

i am using a bound form.
this app was intended to be put together as simply and as quickly as
possible (not my request - the user's).
if there is not commit refresh rate setting then i'll come up with
something else - as long as it doesn't take too much time to figure
out...

thanks,
mc

 

[Albert D. Kallal]

is there any way to make new records appear any faster?
i have 3 laptops networked to a 4th.
all are using a copy of a front-end mdb locally and are linked to the
back-end mdb that lives on the 4th.
users a re complaining that they don't see new records right away and
in fact don't see them till the restart the mdb.
any way to remedy this?

First, you start out with a story about records not being refreshed fast
enough. The, later on, you explain the time delay is FOREVER, and the ONLY
way is to exit the form/table to show the records.

So, in realty, there is not a particular delay time that you're talking
about is there?

Your above text clearly demonstrates this issue.

you have some good suggestions here already, really this comes down to your
design and how you want to approach this problem.

I can't imagine you using Google and having it display every single hit and
search and then than forcing your pour users to work their way thought this
list.

How come Google, or any other system like an instant bank teller system
doesn't have this problem?

The simple solution here is to ask the user what they need to find in the
first place, and THEN display it. This is really the hallmark of design in
just about every computer system you'll use, be it Google, an instant teller
system, or something that you build yourself.

Here is some ideas:
http://www.members.shaw.ca/AlbertKallal/Search/index.html

loading up a form or interfaced to the user with thousands of records is not
only really difficult for the end user, but it's also terrible from a
performance point of view.

 

[mcnews]

First, you start out with a story about records not being refreshed fast
enough. The, later on, you explain the time delay is FOREVER, and the ONLY
way is to exit the form/table to show the records.

So, in realty, there is not a particular delay time that you're talking
about is there?

Your above text clearly demonstrates this issue.

you have some good suggestions here already, really this comes down to your
design and how you want to approach this problem.

I can't imagine you using Google and having it display every single hit and
search and then than forcing your pour users to work their way thought this
list.

How come Google, or any other system like an instant bank teller system
doesn't have this problem?

The simple solution here is to ask the user what they need to find in the
first place, and THEN display it. This is really the hallmark of design in
just about every computer system you'll use, be it Google, an instant teller
system, or something that you build yourself.

Here is some ideas:http://www.members.shaw.ca/AlbertKallal/Search/index.html

loading up a form or interfaced to the user with thousands of records is not
only really difficult for the end user, but it's also terrible from a
performance point of view.

act didactic much?

the app has several ways to search and position the record pointer to
the required data.
what it doesn't have is a means to display new records 9quickly
enough) to other users when they are added.
it probably won't be a big problem as each user should be dealing with
only the person sitting in front of him so shouldn't be concerned
about new records.
somebody asked me so i asked somebody else.
it's a bound form that will sit on top of maybe 300-400 records.
quick and dirty throw-away app that is used to collect data that will
be tossed into SAS thus will live only a short life on a remote
network of 4 laptops for about 6 weeks.
why do people feel the need to make assumptions and make didactic
comments rather than simply answer the question or don't respond.
if access isn't a real database server then so what - we can deal with
it.
harrumph back atcha!