Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Recordset clone not working in Access XP

Status
Not open for further replies.

EVE734

Technical User
Mar 29, 2005
47
US
Hi - I have a control on a form with its control source set to: =Interface_Rejection_Subform.Form.RecordsetClone.RecordCount

(to count the number of records on the referenced subform).
This works fine on non-xp workstations, but for several users who were upgraded to xp, the control shows "?NAME" instead of 0.

Can someone explain what needs to be done for this to work in XP?

Thanks,
Evelyn (and novice user!)
 
Have you tried this ?
=[Interface_Rejection_Subform].Form.Recordset.RecordCount

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886
 
Thanks PH - I just tried it, but am having the same trouble.

Evelyn
 
Use the expression builder to discover how to reference Interface_Rejection_Subform

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886
 
Thanks - When I use the expression builder, there are two ways to select the subform. The options to select from are: Interface_Screening_Form (the main form, which this subform is a part of), Tables, Queries, Forms, etc.

If I select the subform under the "Interface_Screening_Form" choice, the expression is the same (Access puts brackets around the form name, but then drops them when saved).

If I select the subform under the "Forms" choice, it comes up with Forms!Interface_Screening_Subform. However, if I try to use this expression, I get the same #NAME? result that I get in xp.

I appreciate your quick reply and any further advice you may have. I created this database in 2005, and haven't had many issues until this recent upgrade.

Thanks so much!
 
Have you checked the computers that are having problems to make sure that you don't have broken or missing references? Also, could this be a DAO / ADO problem?

Regards,
Lisa
 
Lisa - Thanks, I am having someone from our systems department looking into it right now to see if there was a problem when the upgrade was done to the workstations. As for it being a DAO/ADO problem, I'm afraid I don't much about that. I'm very inexperienced with this. Is there something specifically that I can check?

I do appreciate your time and patience!
Evelyn
 
To check your references, open the Visual Basic Editor in Access on one of the computers that is having problems. Click on "Tools", and then on "References...". The active references will be listed at the top of the list with a check mark next to them. If any references are broken or missing, you will see error messages next to the missing or broken reference names. Please copy the names of the active references into your next post. This information may help explain the problem you are encountering.

Regards,
Lisa
 
Lisa - My apologies for the delay in response. I have finally had a chance to take a look at this, and the active references are as follows:

Visual Basic For Applications
Microsoft Access 12.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.1 Library
Windows Media Player
Microsoft DAO 3.6 Object Library

I don't see any error messages associated with them.

Thanks,
Evelyn
 
So, you've Access2007 on ALL the workstations ?

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886
 
No, on the computers that have not had the upgrade (and where the field is still working), the references are the same, except for Microsoft Access 12.0 Object Library, which is Microsoft Access 11.0 Object Library in the older version. I am somewhat concerned as all workstations are scheduled for the upgrade in early January.

I did just stumble on a website that refers to the problem I am having - didn't have a chance to fully check it out yet, but here it is under "compatibility issues" -
Let me know if this seems to make sense.

Thanks again,
Evelyn
 
Sorry for my confusion regarding XP / 2007. I just knew it was related to a system-wide upgrade being done by our IS dept. I will take a look at the reference and try to figure it out. Thank you.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top