• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 346
  • Last Modified:

Control source keeps changing

Hi
Have a problem that I have not experienced before.
There are five controls on a report; their names and datasources are

text117     =Report!OtherCrosstab!text69
text113     =Report![Comms Crosstab]!text61
text122     =Reports![Summary Crosstab]!BasisOfCrosstabsRequirements_Crosstab.Report!Text71
text128     =Reports![Summary Crosstab]![CrosstabsDecisionAudit subreport].Report!Text71

text 124    =1-([text117]+[text113]+[text122]+[text128])

These controls work fine, all values returned correctly.

Now here's the weird thing. If I make any kind of change to text124, even a change as small as moving the control position a pixel or two, the control source for text122 and text128 changes to

=Reports![Report]!BasisOfCrosstabsRequirements_Crosstab.Report!Text71
=Reports![Report]![CrosstabsDecisionAudit subreport].Report!Text71

and text122, text128 and text 124 then return errors. Then have to reset the source for text122 and text128 and everything is ok again. But it is really bugging. Cannot make any changes without the control sources changing then have to reset them.

Any ideas why this is happening?
Thanks
0
ohgee
Asked:
ohgee
1 Solution
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
Please explain why you are using one report to be the data source of another report.
Reports should only get data from tables or queries, and in some cases open forms.
0
 
ohgeeAuthor Commented:
Difficult to explain why but this is the way I developed it and cannot change it now.
A few controls on the main report (visible = false) reflect control values on four subreports and then another control on the main report sums them. Is this a problem?
0
 
jcampanaliCommented:
My guess is that the basis for the initial report is a Crosstab Query.  Unless you force the column names in the Query Properties, the control source (actually, the field names of the Crosstab) for the report does not exist until the query is run.  So, the way Access is passing through the information, you are running the second report and it is trying to format/print the report before the control source is established by running the crosstab query for the initial report in the background.
0
 
ohgeeAuthor Commented:
I have figured it out, had my references wrong; dropped the   reports!..... from the reference.
Now reads

text 122       =BasisOfCrosstabsRequirements_Crosstab.Report!Text71
text 128       =[CrosstabsDecisionAudit subreport].[Report]![Text71]

thanks for trying to help; appreciate it !!
0
 
DarthModCommented:
Closed, 75 points refunded.
DarthMod
Community Support Moderator
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now