J
Jay Bunten
Just an update on how I fixed this problem.
I appears that calling custom functions in a control on a
form that is member of collection of forms does not work
correctly in ACCESS 2002, or at least it behaves
differently than ACCESS 97.
So I remove the call from the control on the model of the
form. That way when I created a new instance in the
collection there would be no custom call and the form
would load into the collection without getting an error
an closing. The error probably that to do with finding
the custom function since the form isn't really open yet.
Once the form is loaded into the collection I set the
controlsource property of the desired control to contain
the original call to the custom function.
Now the function works as intended.
If MS can shed more light on this subject it would be
appreciated.
Jay
I appears that calling custom functions in a control on a
form that is member of collection of forms does not work
correctly in ACCESS 2002, or at least it behaves
differently than ACCESS 97.
So I remove the call from the control on the model of the
form. That way when I created a new instance in the
collection there would be no custom call and the form
would load into the collection without getting an error
an closing. The error probably that to do with finding
the custom function since the form isn't really open yet.
Once the form is loaded into the collection I set the
controlsource property of the desired control to contain
the original call to the custom function.
Now the function works as intended.
If MS can shed more light on this subject it would be
appreciated.
Jay