> I have some users who are inputting let's say every
> time 15 rows of data. For that I'm planning to use a
> IB_CtrlGrid, so the data is organized in rows already. Is
> this the preferred way, or should I do it in another way ?

Depends on what sort of data.

In an application of mine the users input timesheet details each
week - so obviously there is always 7 days of data. I implement this
via stored procedures using the editsql properties of the query. That
is...

The select sql calls a stored procedure which returns 7 rows whether
they exist in the database or not. The editsql edits a single days
worth of data via a stored procedure which knows to insert/edit/delete
the actual table data depending on the situation.

In this way the user always appears to be "editing" a weeks worth
data, but the database only actually stores information for the days
that have anything worth storing.

This is one of the few occassions when I ise IB_Grid for editing. It
seems to work ok in this situation (there are no memo fields
involved), but there are some complications to getting everything just
right (having to force a refresh of the select stored procedure to see
the changes made by the editsql - since the query cannot be setup to
retrieve just the one record required).


HTH

Geoff Worboys
Telesis Computing