G
Guest
Hi,
I have an Access 2002 application that is run over the network from Windows
XP. The main form has a Treeview control and a subform that shows the record
of the selected item in the tree. I am using the Filter property of the Form
to show only the selected record.
Routinely, but not predictably, a Form_Current event will fire and Access
will point the form to another record (actually, always to the first record
alphabetically). At that time, the Filter property is empty. In other words,
Access loses the Filter property setting.
I have a bit of kludge fix that resets the Filter in the Form_Current, but
if the user was editing a record, it gets saved when the event fires. I'd
rather understand the cause or create a better workaround.
Has anyone seen this behavior before? Any ideas on how to fix this?
Thanks in advance,
Ray Humphrey
I have an Access 2002 application that is run over the network from Windows
XP. The main form has a Treeview control and a subform that shows the record
of the selected item in the tree. I am using the Filter property of the Form
to show only the selected record.
Routinely, but not predictably, a Form_Current event will fire and Access
will point the form to another record (actually, always to the first record
alphabetically). At that time, the Filter property is empty. In other words,
Access loses the Filter property setting.
I have a bit of kludge fix that resets the Filter in the Form_Current, but
if the user was editing a record, it gets saved when the event fires. I'd
rather understand the cause or create a better workaround.
Has anyone seen this behavior before? Any ideas on how to fix this?
Thanks in advance,
Ray Humphrey