Problem with table displays

I'm having a problem with a display with php.

Here's the deal and it may seem complicated.

In Manhatten a block measures 200 feet, so each side of the street the frontage of all the stores should total 200 feet.  
Go trust a client to make sure the data is correct!  Sometimes the block was 130' and sometimes it was 275'.  So what I did was add up all the frontages on left and right sides of the page (2 different variables) , divide those number into 200.  This way I could multiply the individual store frontage by the result that I got to set the height of the rows in the left and right tables for each store front.

The logic works but the results are not correct. I've checked the frontages and they do add up.
The display in the lower left corner shows the left and right frontage totals.  "lm" and "rm" are multipliers that I'm using.

Attachments:
Page 1:
This is what the screen should look like if the client entered the data correctly.  Left and right  both add up to 200 and the multiplier is one.

Page 2:
Left and right frontages are both short.  So I take the multipliers (1.25 for left and 1.42...... for the right), multiply this by the store frontage and use that result to set the height of the table row.

Page 3:
This is where it gets weird.  The left, right and multiplier are the same as on page 1,  but the south street names got forced to the right.

I first posted this at php and was told that I should wrap the tables, so I added the following to the css:

#map_wrap
{
      width: auto;
      height: 220px;
}

I add the <div id="map_wrap"> and the </div> to the code and I get the same results as with out the wrap.

The one thing that I have noticed is the tables appear to be a couple of pixels different in height.

I've also attache the code that displays the tables.
map_lr.php
Map_Screens.doc
breeze351Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Julian HansenCommented:
It would be easier if we could see the rendered HTML - can you post that.

Have you run your html through a validator to determine if the markup is correct - no missing closing tags etc - that is usually what causes things like this.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
breeze351Author Commented:
Got it:

1.  Had width set as 100% instead of "100%"
2.  Did you know that width isn't spelled "wisth"?

It was 2 typos and I've been going nuts looking for logic displays!

Thanks
0
Julian HansenCommented:
I sometimes wisth width was spelled that way ... spelling errors are the bane of my developer existence - so welcome to the club.

Others you are most welcome.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
HTML

From novice to tech pro — start learning today.