>Thanks, Lutz - it is attached...

John,

see attached.

The table does not match te report. It fails with mTech, todaysdate.

for anything else the report works as expected. The address increases as it is to large sometimes, story does not.
You can alter this in the properties on the field there is a checkbox Stretch with overflow on the first page.

The line below the fields in the detail band needs to be closer to the fields and set to Fix relative to bottom of band , so it will follow the stretch of address.

For propper alignment the horizontal line is hidden under the detail band This is a design problem of the report builder. You can mark by blindly drawing a rectangle with the mouse and unselecting any texbox accidently selected by this. (Shift+LeftClick adds ore removes items from selection)

As recomended I have set the grid to pixels.This is better understandable then inches that come in decimal fractions. If you move the line up and down, you might see bottom going into negative. The propper position of the line is on pixel above negative. You can not move the detail band bar and move it back, this will make the detail bar one pixel higher. This is a problem in the builder.

Use the Layout Toolbar to align items.

What I see too:

you have fields named Time_A, Time_B, Exp_12. This looks like the result of a badly created SELECT SQL.

Consider to use
SELECT Cur1.SomeTime AS MeaningfullFieldName,Cur1.PoNum,SUM(Cur1.Numeric) AS Other_MeaningfullFieldName;
FROM YourTable AS Cur1

The AS on the fields / expressions allow to have consistent field names in the result, while the alias in the FROM clause allows the replacement of YourTable by variable name like FROM (cVariableTable) AS Cur1. This might be no problem in your approach, but if the world becomes more complex it is good to be used to this behaviour. As soon as you use subselects it's unavoidable.

If todaysdate shows the date of the current day, what's wrong with simple DATE()?