H
hbear
I have a macro that has been working fine for over a month. It's a simple
setvalue macro that synchronizes user ID on a form and subform. Yesterday,
however, I changed the names of all my forms to eliminate all spaces. I then
went through all macros and code to update all references to the forms.
Everything else in the database seems to work fine, but when I went to enter
data in the subform, I suddenly get the error message "The object you
referred to in a VB procedure is not an OLE object." The Action Failed box
shows the synch macro I referred to.
(The records are saved, in spite of the error message, so it's mostly just
confusing)
The only thing changed in the macro were the form and subform names (i.e.,
[forms]![Enter Orders]![ID] became [forms]![EnterOrders]![ID]) and they
macro's been checked carefully for any unintended changes to spelling or
punctuation. There aren't any.
So does anyone have any idea what's happened?
setvalue macro that synchronizes user ID on a form and subform. Yesterday,
however, I changed the names of all my forms to eliminate all spaces. I then
went through all macros and code to update all references to the forms.
Everything else in the database seems to work fine, but when I went to enter
data in the subform, I suddenly get the error message "The object you
referred to in a VB procedure is not an OLE object." The Action Failed box
shows the synch macro I referred to.
(The records are saved, in spite of the error message, so it's mostly just
confusing)
The only thing changed in the macro were the form and subform names (i.e.,
[forms]![Enter Orders]![ID] became [forms]![EnterOrders]![ID]) and they
macro's been checked carefully for any unintended changes to spelling or
punctuation. There aren't any.
So does anyone have any idea what's happened?