I've searched the site for problems regarding "strange characters" but haven't found this particular problem.
I have a parameter input form which retrieves a set of records that meet those criteria, e.g., area name, beginning labor date, ending labor date, problem code, and building.
The output is to a report with the columns; work order, building, labor date, reported problem, employee, hours worked, labor cost.
In testing, when I enter an area name, beginning date, ending date, problem code, and no building, my subsequent report displays all the data correctly with the exception of the "reported problem" field. In this case, the "reported problem" text comes out with strange characters, e.g., 耎㼂⬑ 錏 ꘀ" for each of the records. See attached.
When I input the same parameters WITH a buildingID, the "reported problem" field prints out correctly, i.e., full text that is in the underlying table.
I suspect that the problem lies in the underlying query, but I’m not sure. I’ll also add that this report has been working for about a year without any problems. It’s just now apparent in my testing environment after an internal customer’s request to modify the input form.
Any help is greatly appreciated.
Thanks in advance!
I have a parameter input form which retrieves a set of records that meet those criteria, e.g., area name, beginning labor date, ending labor date, problem code, and building.
The output is to a report with the columns; work order, building, labor date, reported problem, employee, hours worked, labor cost.
In testing, when I enter an area name, beginning date, ending date, problem code, and no building, my subsequent report displays all the data correctly with the exception of the "reported problem" field. In this case, the "reported problem" text comes out with strange characters, e.g., 耎㼂⬑ 錏 ꘀ" for each of the records. See attached.
When I input the same parameters WITH a buildingID, the "reported problem" field prints out correctly, i.e., full text that is in the underlying table.
I suspect that the problem lies in the underlying query, but I’m not sure. I’ll also add that this report has been working for about a year without any problems. It’s just now apparent in my testing environment after an internal customer’s request to modify the input form.
Any help is greatly appreciated.
Thanks in advance!
