J
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
R
Rick B
Huh?
J
jsccorps
My form is not being updated in a timely fashion.
Are there drawbacks of reducing the Refresh Interval from 60 to 1 second?
Or would it be best to use VB coding to set the Refresh Interval when the
form is opened? If so, could you provide suggested code?
Are there drawbacks of reducing the Refresh Interval from 60 to 1 second?
Or would it be best to use VB coding to set the Refresh Interval when the
form is opened? If so, could you provide suggested code?
D
Douglas J. Steele
I think you're going to need to provide even more details than that.
Are you saying that when you open a form, not all of the data appears?
Where's your data: in the same database, in another Jet database on a
server, in some other DBMS?
What version of Access? What OS on the client? What network?
Are you saying that when you open a form, not all of the data appears?
Where's your data: in the same database, in another Jet database on a
server, in some other DBMS?
What version of Access? What OS on the client? What network?
A
Arvin Meyer
jsccorps said:My form is not being updated in a timely fashion.
Are there drawbacks of reducing the Refresh Interval from 60 to 1 second?
Or would it be best to use VB coding to set the Refresh Interval when the
form is opened? If so, could you provide suggested code?
Refreshing the data makes it available to other users, but it doesn't
requery their forms. Each user must requery his/her own form to get the
lastest changes. OTOH, it is rare that 2 users are working on the same data.
I have 51 concurrent users on one system, over 30 of which are editing data.
I can't remember the last time there was a record conflict.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access Downloads
http://www.datastrat.com
http://www.mvps.org/access
J
jsccorps
Running Access 2003 on Windows Small Business Server 2003.
I am updating controls on a subform based on updates in the main form. The
updates in the subform do occur, but sometimes it takes 10-15 seconds
(sometimes more) to show on the screen. I thought that by reducing the
Refresh Interval would solve the problem.
I tried using Me.Requery - but am presented with the following problem:
The Subform is linked/tied to the Main Form via CustNumber. When I run the
requery (via the Update event), the Subform always brings up the first
CustNumber record in the underlying query. I want the Subform to stay at the
current CustNumber record.
If I do nothing (that is remove the Me.Requery), the Subform does stay at
the current CustNumber record - it just can take a very long time to populate.
I am updating controls on a subform based on updates in the main form. The
updates in the subform do occur, but sometimes it takes 10-15 seconds
(sometimes more) to show on the screen. I thought that by reducing the
Refresh Interval would solve the problem.
I tried using Me.Requery - but am presented with the following problem:
The Subform is linked/tied to the Main Form via CustNumber. When I run the
requery (via the Update event), the Subform always brings up the first
CustNumber record in the underlying query. I want the Subform to stay at the
current CustNumber record.
If I do nothing (that is remove the Me.Requery), the Subform does stay at
the current CustNumber record - it just can take a very long time to populate.
D
Douglas J. Steele
The only Refresh Interval with which I'm familiar relates to ODBC or DDE.
Doesn't sound as though you're using either.
Doesn't sound as though you're using either.