OK.. discecting this post one thing at a time....

> First will this support multiple users with out conflicts?
Maybe. It depends on what you're trying to do and what type of buffering you use. If multiple people try to update the same record at the same time, you'll get conflicts when you do a table update. A view is always local to the machine using it, so just selecting records will not create a problem.

> Do I append blank to the view or the original table?
The View. When you do a table update, the new record will be detected and added to the base table.

> On the lost focus of the cloumn textbox I do = TABLEUPDATE(.T.).
IMO, a bad idea. You should have a Save button. Even worse, (again, IMO), a grid is not a good control for data entry. You should have an Add button. When clicked, a child form opens for data entry.

>I have an app that will be running on a network with 100 plus users. Using VFP 6.0. I have a table that holds hours worked by each user. I have created a pview and then a form with a grid based on the pview. First will this support multiple users with out conflicts? The parameters for the view is a combination of badge number, weekending date, and job number charged too. I have put code in the DoubleClick event of a grid header to add a new entry. Do I append blank to the view or the original table? Then a method runs that removes grid recordsource, closesTables, sets parameters, OpenTables, set the grid recordsource. On the lost focus of the cloumn textbox I do = TABLEUPDATE(.T.). If I doubleclick the header, type in my new job number, then try to doubleclick the header again I get an update conflict. If I move the cursor out of the textbox first I don't get the error. Maybe I am doing this all wrong?