Thank you, subsystems, i'm definitely going to try your method.

Regardless of what you endo up doing, fixed tables or fluid whatever, it's a good idea to write down on the contract that this site is being designed for optimum viewability in such and such resolutions and browsers A, B, and C, versions X, Y, Z, operating systems 1, 2 &3, speed of the connection, etc. Normally that should cover most end users. Say so on the contract. If the client wants more browser versions and resolutions to be tested, you should charge some more. If it is cost effective, like if a lot of traffic is being expected out of handhelds and such, then it works out nicely for both parties. The clients get their website to look good where they want to and you get paid for the extra work.

There is another advantage of writing down the technical requirements of the end users on contracts. If a new version of a browser rolls in and makes something in your website not look good, it is easier to prove to your client that it was not your fault. You can then fix it and get paid for it. Same thing with movie players. Write down what player is required, and if the user needs to enable javascripts. The fact that we write these obvious things in the contracts makes them very long and boring but it has helped in many cases eliminate friction with the client.