Forms won't automatically update (standard behavior?)

[John]

I have a multi-user Access database with back- and front end on the network.
Problem is that the forms don't get refreshed automatically: if user A
enters a record it will only become available to user B if user B closes the
form and re-opens it. I know that I can add a button to the form that does
Me.Requery but I can't imagine there isn't a possibility that does this
automatically and without noticing it. I

Is this common Access behavior? Is there a solution?

I tried to use form timer but that results in unexpected behavior for
instance when it is triggered on the moment a user is entering values in the
form.

Thanks in advance,
john

[Rich P]

Hi John,

Your problem is that you have the same application being used by
multiple users at the same time. The standard practice is to place the
backend on the server and each user has their own copy of the front end.
This will prevent a variety of headaches. The only hassle with this
practice, of course, is when you have to update something on your
application.

VB2005 (VB.Net) has a real nice deployment feature that lets you deploy
anything you want, an MDB application, ADP, excel, word, jpg file... It
is called "Click Once" deployment. The only catch is that it requires
Sharepoint server to be running and IIS.

You can also write a VBscript file in Notepad and call it from a
shortcut on each User's desktop (I had to do this before Click Once).
The VBscript file would check the server to see if there was an updated
version of an mdb front end. If yes, then copy it to the calling
workstation and overwrite the old one. If no, then just start up the
mdb app on the calling workstation.

The other alternative is to manually, go to each workstation and copy
your updated app to it. Even if this is a hassel, it is way less of a
hassel than the problems you encounter by having multiple users using
the same application. When Access says it supports multiple users, they
mean multiple users can use the backend simultaneously - pull data,
edit, update data. Not the front end.

Rich

*** Sent via Developersdex http://www.developersdex.com ***

[John]

Rich,

Thanks for your response. Sorry for not being clearer in my initial post but
each user does have its own front end of the application which is being
updated automatically when he logs in, depending on a 'LastUpdate'
fieldvalue in a backend's table.

The problem is that while users working in the database and having their
forms open their form's datasets don't get updated with the records that
other users add, unless a Me.Requery is performed.

john

"Rich P" <rp*****@aol.comschreef in bericht
news:46*********************@news.qwest.net...

Hi John,

Your problem is that you have the same application being used by
multiple users at the same time. The standard practice is to place the
backend on the server and each user has their own copy of the front end.
This will prevent a variety of headaches. The only hassle with this
practice, of course, is when you have to update something on your
application.

VB2005 (VB.Net) has a real nice deployment feature that lets you deploy
anything you want, an MDB application, ADP, excel, word, jpg file... It
is called "Click Once" deployment. The only catch is that it requires
Sharepoint server to be running and IIS.

You can also write a VBscript file in Notepad and call it from a
shortcut on each User's desktop (I had to do this before Click Once).
The VBscript file would check the server to see if there was an updated
version of an mdb front end. If yes, then copy it to the calling
workstation and overwrite the old one. If no, then just start up the
mdb app on the calling workstation.

The other alternative is to manually, go to each workstation and copy
your updated app to it. Even if this is a hassel, it is way less of a
hassel than the problems you encounter by having multiple users using
the same application. When Access says it supports multiple users, they
mean multiple users can use the backend simultaneously - pull data,
edit, update data. Not the front end.

Rich

*** Sent via Developersdex http://www.developersdex.com ***

[Steve]

That's standard behavior. Forms whether in a stand-alone application or in a
multiuser application do not automatically update with external changtes to
the form's recordsource.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
re******@pcdatasheet.com

"John" <[e-mail] in message news:f4**********@textnews.wanadoo.nl...

>I have a multi-user Access database with back- and front end on the
network. Problem is that the forms don't get refreshed automatically: if
user A enters a record it will only become available to user B if user B
closes the form and re-opens it. I know that I can add a button to the form
that does Me.Requery but I can't imagine there isn't a possibility that
does this automatically and without noticing it. I

Is this common Access behavior? Is there a solution?

I tried to use form timer but that results in unexpected behavior for
instance when it is triggered on the moment a user is entering values in
the form.

Thanks in advance,
john

[John]

Thanks. The biggest problem with this I think is that when users use the
find dialog box after being in a form for half a hour they won't find the
records other users have entered. Is the most common solution for this to
add a refresh button on the form and teach users to press that before
searching?
john

"Steve" <so***@private.emailaddressschreef in bericht
news:it***************@newsread1.news.pas.earthlin k.net...

That's standard behavior. Forms whether in a stand-alone application or in
a multiuser application do not automatically update with external changtes
to the form's recordsource.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
re******@pcdatasheet.com

"John" <[e-mail] in message
news:f4**********@textnews.wanadoo.nl...

>>I have a multi-user Access database with back- and front end on the
network. Problem is that the forms don't get refreshed automatically: if
user A enters a record it will only become available to user B if user B
closes the form and re-opens it. I know that I can add a button to the
form that does Me.Requery but I can't imagine there isn't a possibility
that does this automatically and without noticing it. I

Is this common Access behavior? Is there a solution?

I tried to use form timer but that results in unexpected behavior for
instance when it is triggered on the moment a user is entering values in
the form.

Thanks in advance,
john

[Steve]

Yes, but even that is not foolproof! If another user enters a record
immediately after Refresh and before search, that record still will not be
found.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
re******@pcdatasheet.com

"John" <[e-mail] in message news:f4**********@textnews.wanadoo.nl...

Thanks. The biggest problem with this I think is that when users use the
find dialog box after being in a form for half a hour they won't find the
records other users have entered. Is the most common solution for this to
add a refresh button on the form and teach users to press that before
searching?
john

"Steve" <so***@private.emailaddressschreef in bericht
news:it***************@newsread1.news.pas.earthlin k.net...

>That's standard behavior. Forms whether in a stand-alone application or
in a multiuser application do not automatically update with external
changtes to the form's recordsource.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
re******@pcdatasheet.com

"John" <[e-mail] in message
news:f4**********@textnews.wanadoo.nl...

>>>I have a multi-user Access database with back- and front end on the
network. Problem is that the forms don't get refreshed automatically: if
user A enters a record it will only become available to user B if user B
closes the form and re-opens it. I know that I can add a button to the
form that does Me.Requery but I can't imagine there isn't a possibility
that does this automatically and without noticing it. I

Is this common Access behavior? Is there a solution?

I tried to use form timer but that results in unexpected behavior for
instance when it is triggered on the moment a user is entering values in
the form.

Thanks in advance,
john

[John]

Thanks.
john

"Steve" <so***@private.emailaddressschreef in bericht
news:qV*****************@newsread3.news.pas.earthl ink.net...

Yes, but even that is not foolproof! If another user enters a record
immediately after Refresh and before search, that record still will not be
found.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
re******@pcdatasheet.com

"John" <[e-mail] in message
news:f4**********@textnews.wanadoo.nl...

>Thanks. The biggest problem with this I think is that when users use the
find dialog box after being in a form for half a hour they won't find the
records other users have entered. Is the most common solution for this to
add a refresh button on the form and teach users to press that before
searching?
john

"Steve" <so***@private.emailaddressschreef in bericht
news:it***************@newsread1.news.pas.earthli nk.net...

>>That's standard behavior. Forms whether in a stand-alone application or
in a multiuser application do not automatically update with external
changtes to the form's recordsource.

PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
re******@pcdatasheet.com

"John" <[e-mail] in message
news:f4**********@textnews.wanadoo.nl...
I have a multi-user Access database with back- and front end on the
network. Problem is that the forms don't get refreshed automatically: if
user A enters a record it will only become available to user B if user B
closes the form and re-opens it. I know that I can add a button to the
form that does Me.Requery but I can't imagine there isn't a possibility
that does this automatically and without noticing it. I

Is this common Access behavior? Is there a solution?

I tried to use form timer but that results in unexpected behavior for
instance when it is triggered on the moment a user is entering values
in the form.

Thanks in advance,
john