surprised by parameter query

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

Guest

hi,

i'm finding that there's an unexpected parameter query ('Text14') that
appears when i go to run my report. i thought all i need to do was look
through the names of the half dozen or so controls in the details section
until i come across it and then .... but i'm not even finding any reference
to 'Text14'. so where's it coming from and what do i do about it?

any one care to give me a clue--it'd be really appreciated.
 
it was my first hypothesis -- i found none bore the stamp of 'Text14'. i do
recollect having earlier today renamed one of the controls on the form on
which this report is based (there's a command button on the form which
launches this report) to 'Sum of Target Lesions' from 'Text14' --after that
point, the 'Text14' Parameter Query began appearing when using the cmdbutton.
as best as i have determined the 'Text14' has vanished from the form as well
and is not an issue.???
 
Did you check sorting and grouping?

Ted said:
it was my first hypothesis -- i found none bore the stamp of 'Text14'. i do
recollect having earlier today renamed one of the controls on the form on
which this report is based (there's a command button on the form which
launches this report) to 'Sum of Target Lesions' from 'Text14' --after that
point, the 'Text14' Parameter Query began appearing when using the cmdbutton.
as best as i have determined the 'Text14' has vanished from the form as well
and is not an issue.???
Click to expand...
 
Also, does the old control name show up in any code, such as the command
button's click event, or the report's On Open event?
 
hey guys,

i've gone into the vba editor and searched for 'Text14' throughout the
module and entire project.....and still no cigar???!!!

puzzling stuff.
 
Maybe it's hiding behind another control. Does it show up in the list of
controls at the top left in design view (in the Object box on the Formatting
toolbar)? If it's not in report sorting and grouping, and if it's not in any
of the report's code or in a calculated field (or anywhere else) in the
report's record source query, you could try copying all of the text boxes to
a new report, then all of the command buttons, and so forth until you
generate the parameter dialog again. A similar route to the same place would
be to delete the command button and make a new one, since that seems to be
where the problem lies.
 
i had moved them around a bit to explore your 1st hunch bruce and just got
done with this approach (btw -- i didn't know you could do that) and it's not
amongst the list in the drop down list of objects. it's listed anywhere in
the source query when you run it as a query. i copied all the objects into a
new report and ran it in Preview mode and ...... the parameter query
requesting 'Text14' re-appears again!!??

a good exorcism is what we need.
 
after posting my response, i remembered i hadn't tried re-creating the
command button. i wish i had better news to report but that didn't seem to do
it either.

bummer!
 
You can use the documenter from the Tools menu. Select your report and
choose all properties for controls and sections. Once this is done, you can
print the report and read it.

If you don't want to read it, then close the report and link the table
created by the documenter. On my PC this is C:\Documents and
Settings\hookomd\Application
Data\Microsoft\Access\ACWZUSRT.MDT;TABLE=doc_tblObjects

You can then create a query to find your error:
SELECT doc_tblObjects.Name, doc_tblObjects.Extra1
FROM doc_tblObjects
WHERE (((doc_tblObjects.Extra1) Like "*Text14*")) OR (((doc_tblObjects.Name)
Like "*Text14*"));
 
duane,

it's only a nine page report and so it seemed easier to read it than create
the query and still no cigar!! as a 2ble check, i exported the report to
'rtf' and searched, in vain, for 'Text14'

double bummer.
 
Did you look at Sorting and Grouping? With the report open in design mode,
click View > Sorting and Grouping?
You wrote " it's listed anywhere in the source query when you run it as a
query". Did you mean to say it's not listed, and if you run the query by
itself it doesn't ask for parameters?
 
bruce,

i contacted ms tech support services and we were able to decode the enigma.
the problem lay with the fact that when i created a combobox on a form and
then copied the combobox onto the report it retained the Text14 name that it
was given on the form. later i changed the name on the report from Text14 to
Cycle. at that point it started to request the value of Text14. so, now if i
revert to Text14 all's well w/ the report. adding a new Cycle control from
the field list works just as well. and it's been suggested that in future
when adding new controls to a report from related forms that not copying them
is a better strategy.

-ted
 
Glad you got it solved, but I'm a bit puzzled. Saving a form as a report is
actually a very good way of making a report, provided the form works properly
in the first place. Copying controls may be another matter. If the report
or a related query kept looking for Text14 it's because Text14 is still in
there somewhere. Renaming a control shouldn't matter unless something else
(such as a calculated text box) is trying to refer to that control. I'm
curious as to why you wouldn't investigate sorting and grouping.
 
i thought i did relate that i looked into the sorting and grouping fields and
that there was no sign of the infamous Text14 to be found. also, this is
probably not clear from my description, the report pre-existed the request
add the 'Cycle' combo box to the form. once the form got the benefit of the
'Cycle' combo box, i underook to copy and paste it onto the pre-existing
report. in future, i will use the 'List' of controls on the target
form/report when adding controls to avoid this kind of thing.

-ted
 
Back
Top