Grid or Table Component?

[Rob Cozens]

> Or are we stuck with the old
>HyperCard technique of storing each element of a single list of data
>separately in adjoining fields and managing their scrolling
>synchronization in a script?

Hi Dan,

There is another old HC technique that works well for me:

1. Create a single scrolling field with a non-proportional font (eg:
courier, monaco)
2. Pad text with trailing blanks and numbers with leading blanks to create
a fixed-format record for each line
3. Paint (in HC, position grid lines in RR) lines on the screen to create
columns.
4. Provide individual fields below the scroll field for entry of new items.

This solution may be low-tech, however it can also be a powerful
table-management tool.  I have written handlers to:

1.  Add a record to the table in ascending or descending order based on a
key value anwhere in the record.
2.  Select a record from the table based on key value
3.  Change any portion of a record
4   Delete a record based on key value
5.  Retrieve any portion of a record

If you would like to see how this translates visually, visit
http://www.oenolog.com/oenotes.htm and look at the screen shots for
first-level screens under the Wines, Vessels, & Setup menus.

Rob Cozens
CCW, Serendipity Software Company

"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."

from "The Triple Foole" by John Donne (1572-1631)