Report Control Problem

[tkosel]

I have a text box on a report at a customer site that contains the following
as a control source:

="Group Membership report for: " & Chr(13) & Chr(10) & [GROUP_NAME]

This string appears in the actual text box on the screen in design mode, but
NOT in the control source of the property for that text box.

When I run the report, #NAME appears in that text box.

If I try to edit the control source field in the properties window, It tells
me that "The function you entered can't be used in this expression." Also
some other stuff. The bottom line is that is doesn't like the Chr(13) &
Chr(10), if I take that out, the error goes away. This used to work at their
site just fine.

All this works fine on my development machine right now. Any suggestions?

 

[John W. Vinson]

If I try to edit the control source field in the properties window, It tells
me that "The function you entered can't be used in this expression." Also
some other stuff. The bottom line is that is doesn't like the Chr(13) &
Chr(10), if I take that out, the error goes away. This used to work at their
site just fine.

All this works fine on my development machine right now. Any suggestions?

Any time you see a builtin function being unrecognized - *especially* if this
happens on one machine and not another - the place to look is a References
problem. On the machine where this isn't working, open the VBA editor and
check Tools... References. If one is marked MISSING that's the source of the
issue. Either uncheck that reference (if it's not something you actually need)
or correct the path to the .dll file that's marked as being missing.

 

[tkosel]

Mr. Vinson,

Thanks for your quick response. You suggestion is definitly important to do.
I always do that when I have this kind of a problem, however, there are no
missing reference(s). I have been fooling with it, and solved the problem,
but don't understand exactly why it worked.

I selected the reference titled "Microsoft DAO 3.6 Object Library". (It
indicated that it was pointing to "C:\Program Files\Common Files\Microsoft
Shared\DAO\dao360.dll".) When I had it selected, I clicked the Browse button
and browsed to the same location indicated. When I did that, came out, saved
the changes, exited Access and restarted, the problem was solved! My plan was
to start at the bottom and work my way up, but the first one I tried worked.
(I am using 7 references total.)

Any ideas on why my actions worked and why this happened?

 

[John W. Vinson]

Mr. Vinson,

Thanks for your quick response. You suggestion is definitly important to do.
I always do that when I have this kind of a problem, however, there are no
missing reference(s). I have been fooling with it, and solved the problem,
but don't understand exactly why it worked.

I selected the reference titled "Microsoft DAO 3.6 Object Library". (It
indicated that it was pointing to "C:\Program Files\Common Files\Microsoft
Shared\DAO\dao360.dll".) When I had it selected, I clicked the Browse button
and browsed to the same location indicated. When I did that, came out, saved
the changes, exited Access and restarted, the problem was solved! My plan was
to start at the bottom and work my way up, but the first one I tried worked.
(I am using 7 references total.)

Any ideas on why my actions worked and why this happened?

I've never understood the phenomenon well enough to hazard a guess. My
impression is that there may be something subtly "wrong" with the linkage to
the dll and that just looking at the file somehow resets it, but I'm sure a
Windows systems person would have to smother their laughter at my suggestion.