Your page is constructed from a single, incredibly complicated table. This table is kept together by blank images, that are defined in the last row of the table.
This is a very outdated approach and while it is commendable that it only uses one table, it still is much more complex than it needs to be. We've stopped slicing images in HTML a few years ago and it works much better now.
On to the problem. As I said, the browser receives actual information on columns on the very last row of the table. Before that, it knows that the table is certain pixels wide. It knows that there are more columns than it's rendering, since all early cells span multiple columns and rows. Lacking clear direction, browsers end up approximating column widths. IE approximates wrongly.
When you put your page into full screen mode, browser has to redraw the table. Now that the last line of the table was loaded and there are no more issues as to how wide the columns are, IE can render the table correctly.
While I think this approach could be dealt in a much better way, you didn't come here to be taught on best approaches in web building. You wanted your page not to look crooked. I don't work with tables a lot these days, but I think that moving the last table row to be the first one (and thus define the sizes of the columns right at the beginning), should help browsers render the entire table correctly.
[small]Do something about world cancer today:
Comprehensive cancer control information at PACT[/small]
