Overlapping Fields

[pharrison74]

I have a few fields that are giving me issues with overlapping. I don't see the issues on the other reports and they are setup the same way.



I have 2 fields stacked for layout and both are set to Can Grow. For some reason the top field is overlapping the bottom field and I am unsure why.



Thanks
Pete

[rpeare]

can you provide a sample database? this would be hard to diagnose without one.

[pharrison74]

OK, here is the database with junk data.

If you open the DFO and Litigation Potential report...Ignore the error that pops up. That just started showing up after deleting a field that I never even used. You will see the overlapping in the fields.


Testing_Litigation_DB1.zip

Thanks
pete

[rpeare]

You used the report wizard to generate this I'm guessing and, to me, the report wizard makes way more errors/problems than makes it worth using.

To remove the layout (which is forcing this bad behavior) you can RIGHT CLICK one of the fields. You'll notice a dashed line around the selection, choose LAYOUT from the pop up menu, select REMOVE LAYOUT.

Run the report.

I'd suggest not using the report wizard at all, if you want to customize it at all you have to redo a bunch of settings (like the grid from 10x10 to 24x24) to get it back to the 'default'.

[pharrison74]

No this one was built from scratch. The problem with removing the layout that I create is then the field gets pushed down by others in the other columns when their data grows.

[rpeare]

well the only other suggestion I can offer is that you make the two subsections their own subreports with and create two subreports on the main form. Access tries to line up fields on the same 'row' when it produces the report except when the 'layout' feature is used but you've seen the drawbacks to both and the only way I can think of is subreports of a single field.

[cyanidem]

Or you can combine fields Status and Status_Internal in record source of report (the same with Background and others):

combinedStatus:[Status] & chr(13) & chr(10) & [Status_Internal]

Then use a single field combinedStatus in report instead of two fields. Only thing is you'll loose possibility of using different colours for them. Unless there's a way to produce string with html tags in query of which I'm not sure about

[rpeare]

Yep, the different colors was the only thing that prevented me from suggesting that.

[cyanidem]

Oh well, tried out of curiosity and it works:



Text in query is build this way:

combinedBackground: [Background] & Chr(13) & Chr(10) & "<font color=""blue"">" & [Background_Internal] & "</color>"

Also, text box on report must have Text Format property set to "Rich Text". And a little trick - you can't change that property unless you save record source for report as static query (not SQL).
(Static query? Is that a proper name for it? Sorry, but English is not my first language...).

Edit: Small change, I realized after posted screenshot. Apparently there's no need for closing tags and it works better without it. Also chr(10) & chr(13) have no effect at all, better to use html <br> tag.

combinedBackground: [Background] & "<br><font color=""blue"">" & [Background_Internal]

[pharrison74]

Do I create a new module for this code?

I tried to change the report to static query,. However still get the error for trying to change the field to Rich Text

[cyanidem]

Open report in design mode, click on the elipse next to Record Source property, that will open source query:



Then on the ribbon click Save As:



Give it some name, save and close the source. Check if Record Source of the report now points to that new query and you should be able to change Text Format to rich text now.

[pharrison74]

Yeah was able to do that yesterday but it still complains.

[cyanidem]

No idea why. Can you upload it?

[pharrison74]

Testing_Litigation_DB1.zip

Here you go.

[cyanidem]

There's no "combined_background" nor other "combined" fields in your query as I suggested in post #7 (and #9).
Take a look how it's done in attached db. Mind that there's only Background and Status fields combined into one, I was too lazy to do them all

Testing_Litigation_DB1.zip