Sub-form stops working in 2003

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

The same sub-form which I use on a report and a form has stopped working for
some 2003 and users. It works on 97, 2000, and 2002. The sub-form is part of
a continuous form and report. Is there a problem in 2003?
 
It is most likely a Reference problem. Check your references in the VBA
editor under Tools-->References to see if any are missing.
 
Thanks for the input. I am not sure what could be missing, that would not
stop the whole database working.

The references I would expect to see for my application are VB for
Applications, MSAccess 11, MSDao 3.6, OLE Automation, MSVB for App Ext 5.3.
We checked with a user and she had these references.

In looking at a development machine here, we did notice more references to
VB for Applications which were not checked off. I do not know what these
other references come from.
 
A missing or incorrect reference could stop your whole database from working.
You only mentioned one subform that is not working correctly. Is there
anything special about that subform, for example, are you using any add-ins,
ActiveX controls, etc. that are unique to that subform? Have your tested
every other form and subform to be sure they are not failing?
Does the subform have a module? If so, step through it in debug mode to see
where it it failing.
When you say it doesn't work, what is happening or not happening?
 
Thanks again for the feedback -

I will test the things that you mention, but for now

there is no module

the subform does not list the data I would expect to see, in one case on the
report, it lists data for the first record only, and not for subsequent
records. In another case the form as well as the sub-form show no data, as if
the link is broken.

The report I have the subform on is continuous, the form I have it on is not.

I have replace all the objects in connection with this process, but this
does not help.

Some additional information not directly related to the subform also happen
for some 2003 users. We have a button that copies the data entry screen data
to a new record. That does not work for a handful of users. And a search
mechanism throws a few users out of the database when what they are searching
for is not in the database.
 
Back
Top