Fireworks HTML isn't meant to be used for live production websites. It's meant for prototypes. Once you're happy with the prototype, you take the graphic assets and build proper HTML from scratch, in a system like Dreamweaver (or any other HTML authoring application).
There's no sense in worrying about validation errors for that garbage code that Fireworks creates. It's like rearranging the deck chairs on the Titanic as they say.
Thanks for the response . . .BUT I am only using Fireworks (CS4) to create interactive menus to place into Dreamweaver, - yes they can be done with I suppose "cleaner " CSS but I find building menus etc easier than with css
As an example the errors occur on the page below and seemingly, most are due, from what I can see, because of Fireworks CS4 - used both for the Main title bar in the header and for the Catalog menus - my question is how do I define "undefined " in the code that is transfered form Fireworks to Dreamweaver as this seems to cause the errors
Heres a page www.Greenlinehose.com/catalogs.htm
it gives similar errors to all pages where fireworks menus are involved
This I hope is resonably clear, If not I apaologize and can try again
Thanks for your time and patience
"Easier" doesn't always mean "better". If you take a look at the code you've supplied, you'll see that this is being caused by the inclusion of spacer gifs - which also means a table based layout as well - again, not best practices. The source code on the sample site you've provided is quite bloated for just that top menu and a great deal of that code is just for spacer gifs to hold the table open.
If you're builidng sites professionally I'd recommend learning how to do things in a best practices manner and generally that means using an unordered list along with CSS for styling the navigation. You'll waste more time trying to fix the FW menus than you will learning to do things in a best practices manner. Way less code and a much more accessible menu. It's not that hard; I can get students creating CSS menus in under 3 hours when they've never done it before. If you're looking for easy without digging into the code yourself, consider commercial options such as the huge variety of CSS-based menus found at projectseven.com. They're well made, accessible and plug into Dreamweaver.
If it's just a hobby, then don't worry about it. As long as it works, you're fine.
But thank you for your comments. I made some decisions at the beginning, that upon looking back I regret. The site started about 21/2 years ago, I was given the design by the company and suggested that it work, their in house person was going to update. I chose tables over CSS thinking it would better suit his abilities, and I was just starting CSS, it became "make it fit"- after that and it works. I note this last revision - I am now, I guess, the one making changes. That revisions to "menus" take a bunch longer than adding or changing items in a list controlled by css, has become obvious (painfully) but the daunting prospect of redoing the entire site (in both languages) isn't a warming thought either.
Thanks for the patience and response - it is indeed by the way a bit of a hobby, or retirement income additive - I charge for work time, not learn time and keep my hand in . . . .apparently not so well . . . .
Sorry, Greg. I hope I wan't too brutal.