We have sites with many tables. How does ComWeb cope with these ?

ComWeb V4 has adopted the W3C recommendations regarding tabular presentation of data. This involves management of the content separately from the presentation (structure).
Refer the following link for further details.

Techniques for Web Content Accessibility Guidelines - Avoid tables for layout

If tables are used for record based data (ie row/column) there are many tabular list components with automatic pagination. We recommend loading record based content into a database table (see ComWeb_CorporateData database), and using Corporate Data Queries to extract and display the data. After the query is created (refer Tech Support) the Content Manager can include an entire table with styling, content and pagination using only 1 ComWeb display component.

If tables are used for structural display of information with various levels of indent, this can be achieved via CSS and a multi-level STYLE construct. This is easy to achieve in ComWeb, with the advantage of W3C compliance and possible removal of tables for layout and presentation purposes. Removal of table definitions in ComWeb will greatly simplify page construction, with an increase in maintainability and reduction in support requirements.

What may have been a large complex site previously with a high reliance on technical developers, may turn into a ComWeb site that is easy to navigate and maintain by subject matter experts - without a requirement for technical abilities or assistance - and benefit from the other advantages of a Content Management System. Contact CompuCraft for a recommendation or assistance with data/content migration to ComWeb.