Grids work well--they're not simple, but very doable. Most of us depend on them in one form or another (no pun intended). Do your collegues mean using the Browse window? If so, then I'd agree that it is better to use a form with a grid on it.

There are many techniques. Here's my favorite (where it's possible). I use grids to display data but then I will arrange textboxes, comboboxes (and so on) on the form for doing the actual data entry. I came to this because grids can get very slow when they depend on controls other than textboxes. And, it's somewhat of a pain (IMO) to maintain controls.

I (generally) use row buffering for parent tables, and table buffering for child tables. Or I use a view to populate the grid. In which case, I would possibly use table or row buffering.

There was just recently a verrrrry long thread on buffering and different opinions. Perhaps if you search for thread on buffering you will find some posts that are useful.

Good luck, and post here with specific questions as you get going.

>I'm new at Visual Foxpro programming, and my collegues warn me of using the grid directly as a data entry form - saying something about buffering of tables that mess-up my data. How true is this?
>
>Is there any way to go around the problem but still use the grid for data entry? Because it would be awkward for users to enter information on another window and only have the grid reflect what was entered, especially when entering order slips, delivery receipts, invoices, etc.
>
>Are there any reading materials that can help explain how to manipulate the grid better?
>
>Thanks in advance for any help offered.