Basic spreadsheet layout: some basics about designing templates for use by other people. (For Developers) (column)

BASIC SPREADSHEET LAYOUT

There is no best way to structure a worksheet, but there are many bad ways. This article will help you identify and avoid layout problems before they occur. The problems we'll discuss are caused by that necessary evil of all worksheet templates: the user. There is no way to construct a truly indestructible template, but you can minimize the chances of a user damaging your models.

We'll focus on applications that reside entirely on the worksheet, and we'll assume that you're working either with 1-2-3 Release 2 or higher or with Symphony. Symphony users should also refer to the "Symphony Models" box on page 48. These observations should help avert disaster while you're creating a model and later when it's pressed into service.

FREEDOM

The first issue to consider in designing a worksheet is that of control versus versatility. If your model is macro-driven and provides no escape from macro control, your worksheets can be relatively unstructured with impunity. You must still consider whether the macros will insert and delete rows or columns, whether you've left room for the worksheet to expand as needed, and whether you've left room in which to modify the macros themselves if the need arises.

Whether the model is entirely macro-controlled or not, your worksheet will probably contain several different work areas. These will normally consist of the user's work area, the developer's workspace, and common areas. …