Issue with fields running into one another (sporadically)

[karbar]

I have a report with 340 names...there are five fields grouped under a
location code.

The report looks great EXCEPT twice within the report the first name field
runs directly into the last name field (Last name field is displayed first)
this happens twice within the reports on the same two employees each time.
There are no other characters within the last name or first name field except
the actual names.

If you export the report to Word, this formatting quirk doesn't happen.

Any thoughts on where to look to fix this?

 

[Chuck]

I have a report with 340 names...there are five fields grouped under a
location code.

The report looks great EXCEPT twice within the report the first name field
runs directly into the last name field (Last name field is displayed first)
this happens twice within the reports on the same two employees each time.
There are no other characters within the last name or first name field except
the actual names.

If you export the report to Word, this formatting quirk doesn't happen.

Any thoughts on where to look to fix this?

Replace the two fields with one text box.
In the text box type: =[<name of last name field>] & ", " & [<name of first
name field>]
Width of text box must be large enough to accommodate the longest last name/
first name combination plus the coma and a space.

Chuck
--

 

[Klatuu]

The only thing that causes this is when the two controls are touching in
design vew and the length of the last name is too long to fit in the space
allowed in the control.

For example let say we have John Smith and Wally Parkensburgerosthchild.
It could look like

Last First
Smith John
ParkensbWally

 

[karbar]

Klatuu,

In design view the fields do not touch.

ALSO...the two names this consistently happens on are 6 characters
long...and there are longer names (the longest is 10 characters) and the
smooshed together effect does not happen on those records.

I was able to get the behavior to stop by adding another fake record to the
database then deleting that record, and now the report prints fine...I have
absolutely no idea why. Now that I've done this, I can recreate the
behavior.

Thanks for your help though...I do appreciatte it.

 

[karbar]

Sorry, I meant I cannot recreate the behavior now....