Line Spacing on a Report.

[vincet2009]

Hello Everyone,

I am trying to make a report look better than it does now. The problem I am having is that the line spacing on one feild is being affected by the spacing of another. Take a look at the jpg that I have attached. This is explains it much better.

Thanks in advance.

Vince

 

[KenHigg]

I've seen the problem posted earlier. I suppose you got no where with it huh?

Seems to me that if you moved 'Gilroy, CA' to the line directly under '7030 Rosanna St' then the 'Occupancy Check' data '4/14/08 VA' would appear to associated with it and not '7030 Rosanna St' record?

 

[dkinley]

Heh.

By the image you posted, I would assume that you have 2 fields for the address. Also, the Occupancy Check field is probably set 'to grow' with the result being the second address field is pushed down. This is also evident in the Notes column because it stays together and not pushed down.

To rectify this, you will need to concantenate the two address fields into a single unbound control. You can even add a line return character into the expression so the city and state appear on the next line.

Basically, the data source of the address control should look something similar to the following .....

= [AddressStreet] & vbCrlLf & [AddressCity] & ", " & [AddressState]

Rename the fields as appropriate to what is the underlying data source of the report.

The spacing for the checkboxes, etc., are the result of the same. A workaround might be to alter the Occupancy Check control to cover a larger area so that the bottom edge of the control is past all the other controls in the detail section. This way, they should not be pushed down when it starts growing.

-dK

EDIT: I say should not be pushed down because I can't remember if it based on the first line in a control or the bottom edge - but worth a shot.

 

[vincet2009]

Hi Ken,

You are right. I got nowhere last time. So here is the deal. The city, Gilroy, CA is indeed right below the Address, 7030 Rossanna St. The problem is, becuase the Occupancy Check feild has so much data in it, it automatically moves everything else down. I know I did not mention this on the screen shot, but if you look at the check boxes for Occupied, In Contract and Assigned to Inspector? Those too are moved down becuase of this data. Any help would be great.

 

[KenHigg]

I would suggest placing the check boxes side by side instead of one over the other. Thats the only solution I can think of.

Edit: Scratch that...

 

[vincet2009]

Hello DK,

So forgive me for being stupid but how exactly do I do this. Do I go to the properties of the Address Felid and enter the statement you gave?

 

[dkinley]

Correct. Delete the field name in the control source of the address and put in what I posted. The field names in brackets will need to be renamed to what you have them.

-dK

 

[KenHigg]

I would move the occupancy data down to the bottom of the report under the assigned to inspector check box.

 

[KenHigg]

Heh.

By the image you posted, I would assume that you have 2 fields for the address. Also, the Occupancy Check field is probably set 'to grow' with the result being the second address field is pushed down. This is also evident in the Notes column because it stays together and not pushed down.

To rectify this, you will need to concantenate the two address fields into a single unbound control. You can even add a line return character into the expression so the city and state appear on the next line.

Basically, the data source of the address control should look something similar to the following .....

= [AddressStreet] & vbCrlLf & [AddressCity] & ", " & [AddressState]

Rename the fields as appropriate to what is the underlying data source of the report.

The spacing for the checkboxes, etc., are the result of the same. A workaround might be to alter the Occupancy Check control to cover a larger area so that the bottom edge of the control is past all the other controls in the detail section. This way, they should not be pushed down when it starts growing.

-dK

EDIT: I say should not be pushed down because I can't remember if it based on the first line in a control or the bottom edge - but worth a shot.

Thats going to get clunky as there are issues with the agent data area as well

 

[dkinley]

Ken - agreed. Noticed it could get whacked trying to solve them all so edited to see if the bottom edge was the push trigger.

But, if none of the above work, I agree with Ken -- redesign the layout. I normally do not run into these issues because I design my reports so that I don't run into them. In my seriously noobish days I didn't know how to overcome these sorts of things so started adapting presentation styles as workarounds that were pleasing to the eye but yet informative. I've not changed that habit because it works and saves me time.

-dK

 

[vincet2009]

Okay. Thank you all. I will give it a try and let you know what happened.

Thanks again.

 

[KenHigg]

Ken - agreed. Noticed it could get whacked trying to solve them all so edited to see if the bottom edge was the push trigger.

But, if none of the above work, I agree with Ken -- redesign the layout. I normally do not run into these issues because I design my reports so that I don't run into them. In my seriously noobish days I didn't know how to overcome these sorts of things so started adapting presentation styles as workarounds that were pleasing to the eye but yet informative. I've not changed that habit because it works and saves me time.

-dK

And I always try to put any repeating data at the bottom of the report detail section as a rule of thumb...

 

[vincet2009]

DK,

I have 2 fields (Address and City) The one called City is really the City and State in one Field, for example Gilroy, CA.
Okay, I went to the Control Source on the Address and changed it to the following:

= [Address] & vbCrlLf & [City] &

For some reason, it does not save this info in the control source. It keeps showing me the original data which is 'Address'.

 

[dkinley]

Remove the last ampersand - & - so it reads ...

= [Address] & vbCrlLf & [City]

and ensure it is in the Control Source property.

-dK

 

[KenHigg]

You may need to resest the 'can grow' property to true - ?

 

[vincet2009]

Okay,

SO now it took, but when I run the report it comes up with a Enter Parameter Value Box. Is the text between the & symbols supposed to be vbCrlLf. In other words, is that a small L and then a big L?

 

[KenHigg]

It's supposed to be vbCRLF and is not case sensitive...

 

[dkinley]

I suspect the parameter box is because you haven't named the field names correctly (in the brackets for address and city).

If you are putting data into a report from a query or table, check the source and verify that those are the correct field names.

Capitalization shouldn't matter on the vbCrLf (thats for a line feed so the second part appears on the next line) but it might be a matter of where my head is.

I know it will work in a MsgBox for forms, but just threw it out there for a report because I couldn't remember. You can swap that out with Chr(13) or Chr(10) which are carriage return and line feed respectively to see what a report will use.

-dK

 

[vincet2009]

Nope. Same thing. The field names are correct. The Enter Parameter Value window shows vbcrlf as the command that it does not understand. Could it be because I am using Access 2003?

 

[KenHigg]

I couldn't get this to concatenate on the form either. Do it in the recordsource...