SOS Registered Lunatic Local time Today, 05:29 Joined Aug 27, 2008 Messages 3,514 Feb 12, 2010 #21 Oh, and the Access help file is sometimes not as accurate as it should be.
F falcocom25 New member Local time Today, 08:29 Joined Feb 28, 2012 Messages 2 Feb 28, 2012 #22 I figured a way to bypass this issue by using the form timer. 1- Set the timer to a very high number on the Current or Load event. Private Sub Form_Current() Me.TimerInterval = 90000000 End Sub 2- Requery on the Timer event and reset timer interval to the high number. Private Sub Form_Timer() Me.Requery Me.TimerInterval = 90000000 'Reset timer interval End Sub 3- On your Delete event set the timer interval to one millisecond so that the form is re-queried right away. Private Sub Form_Delete(Cancel As Integer) Me.TimerInterval = 1 End Sub Not too elegant but it works! You are welcome.
I figured a way to bypass this issue by using the form timer. 1- Set the timer to a very high number on the Current or Load event. Private Sub Form_Current() Me.TimerInterval = 90000000 End Sub 2- Requery on the Timer event and reset timer interval to the high number. Private Sub Form_Timer() Me.Requery Me.TimerInterval = 90000000 'Reset timer interval End Sub 3- On your Delete event set the timer interval to one millisecond so that the form is re-queried right away. Private Sub Form_Delete(Cancel As Integer) Me.TimerInterval = 1 End Sub Not too elegant but it works! You are welcome.
T TheSmileyCoder Registered User. Local time Today, 14:29 Joined Dec 17, 2012 Messages 15 Dec 17, 2012 #23 Instead of using a very high number for the timer event, just set it to 0 when you are not using it: Me.TimerInterval = 0 This disables the timer event from occuring until you re-enable it by your existing code Me.TimerInterval = 1
Instead of using a very high number for the timer event, just set it to 0 when you are not using it: Me.TimerInterval = 0 This disables the timer event from occuring until you re-enable it by your existing code Me.TimerInterval = 1
M mdlueck Sr. Application Developer Local time Today, 08:29 Joined Jun 23, 2011 Messages 2,650 Dec 17, 2012 #24 I did not read through the entire thread in detail... appears no solution found yet, so tossing this out as having been the root cause several times... Must update RecordSource in order for Refresh to actually work http://www.access-programmers.co.uk/forums/showthread.php?p=1091968#post1091920
I did not read through the entire thread in detail... appears no solution found yet, so tossing this out as having been the root cause several times... Must update RecordSource in order for Refresh to actually work http://www.access-programmers.co.uk/forums/showthread.php?p=1091968#post1091920
T TheSmileyCoder Registered User. Local time Today, 14:29 Joined Dec 17, 2012 Messages 15 Dec 17, 2012 #25 Actually a work-around was posted. Changing the recordsource forces a requery, at which point a refresh is just redundant.
Actually a work-around was posted. Changing the recordsource forces a requery, at which point a refresh is just redundant.
M mdlueck Sr. Application Developer Local time Today, 08:29 Joined Jun 23, 2011 Messages 2,650 Dec 18, 2012 #26 TheSmileyCoder said: Actually a work-around was posted. Changing the recordsource forces a requery, at which point a refresh is just redundant. Click to expand... Also redundant to have to reset the RecordSource to what it already is set to. Very odd code behavior!!!
TheSmileyCoder said: Actually a work-around was posted. Changing the recordsource forces a requery, at which point a refresh is just redundant. Click to expand... Also redundant to have to reset the RecordSource to what it already is set to. Very odd code behavior!!!
