Paul

You can have your grid with the target table as its DataSource but set the table's "buffering" so that updates don't take place till you commit them.

In the form's Data Environment (DE), set the table's BufferModeOverride to the value you wish (2-5) depending on whether you'll be committing several recs at one go or not (see "Buffering Data" et al in Help).

You use TableUpdate() or TableRevert() to commit or cancel your changes (say in the click event of save and undo buttons), along with Transaction processing if you wish (see "Begin Transaction").

Alternatively you could have a xaction table to take your grid additions/amendments and write them to your main table on save. You can have the table set up as per Cetin's code or do it visually with the grid builder, or through its properties.

HTH

Terry

>I am a new foxpro programmer working with a grid.
>
>I want to use a grid without a data source to collect information, and then, if it stacks up, save some of it to a table.
>
>However, when I run my grid, it seems to be read-only, that is, I can't enter anything in it. Is this normal for grids without record-source or control-source? If so, what is the normal way of collecting non-databound info???
>
>Thanks,
>Trimtrom