B
Buddy Weaver
Access 2000.
I have a continuos form called Name_List, which shows a
list of names.
the user clicks a button by one of the names and a
Name_edit form is opened.
when the user is finished editing the name, they click OK
and return to the Name_List form. at that time, the
Name_List form is requeried to show the changes.
this works fine with windows 98 and has form several
years.
problems arose when users starting getting windows 2000.
if the operating system is windows 2000, the following
happens.
when the user closes the Name_edit form and the vb code is
run to requery the Name_List form, a run time error occurs
(3240) saying the object is no longer valid.
if the Name_List form is closed and re-opened it shows the
updated data.
what is the difference in windows98 and windows 2000. the
code is simple. it just requeries a form whose record
source is a query.
works fine in windows 98 but not in windows 2000.
I have a continuos form called Name_List, which shows a
list of names.
the user clicks a button by one of the names and a
Name_edit form is opened.
when the user is finished editing the name, they click OK
and return to the Name_List form. at that time, the
Name_List form is requeried to show the changes.
this works fine with windows 98 and has form several
years.
problems arose when users starting getting windows 2000.
if the operating system is windows 2000, the following
happens.
when the user closes the Name_edit form and the vb code is
run to requery the Name_List form, a run time error occurs
(3240) saying the object is no longer valid.
if the Name_List form is closed and re-opened it shows the
updated data.
what is the difference in windows98 and windows 2000. the
code is simple. it just requeries a form whose record
source is a query.
works fine in windows 98 but not in windows 2000.