G
Guest
Some time ago (3-4 years) I remember discussions about the performance issues
of Requery vs Refresh. I know that 'RunCommand acCmdRefresh' superceeded
(replaced) DoMenuItem, 5...' in the late 90's. Supposedly ( as my memory
serves) Refresh was better for performance than Requery because it just
posted back the 'old' view of a list box or dropdown box rather than
rerunning the underlying query.
From what I am reading in Discussion Groups recently the replacement for
DoMenuItem, 5... is Me.objectName.Requery. What happened to Refresh. It is
not even available as an option for 'Me.ObjectName' but is still available as
'RunCommand acCmdRefresh' What about performance issues? Has hardware and
software improvements nade this a moot point?
I am running A2000 but getting to update to 2007. Am I going to have
problems with performance in dbs still using the esoteric (outdated and
possibly un-supported)code?
of Requery vs Refresh. I know that 'RunCommand acCmdRefresh' superceeded
(replaced) DoMenuItem, 5...' in the late 90's. Supposedly ( as my memory
serves) Refresh was better for performance than Requery because it just
posted back the 'old' view of a list box or dropdown box rather than
rerunning the underlying query.
From what I am reading in Discussion Groups recently the replacement for
DoMenuItem, 5... is Me.objectName.Requery. What happened to Refresh. It is
not even available as an option for 'Me.ObjectName' but is still available as
'RunCommand acCmdRefresh' What about performance issues? Has hardware and
software improvements nade this a moot point?
I am running A2000 but getting to update to 2007. Am I going to have
problems with performance in dbs still using the esoteric (outdated and
possibly un-supported)code?