Neil,

You do not need unique ID to display information from table in the view (if you are not going to somehow limited this information based on user criteria).

Update SQL command is very straight-vorward. As in VFP Help:
Update table ... set field_name=... where ....

Also if you have indexed table, you may set relation, scan for updated records in the view, scatter memvar in the view and gather memvar on table.

>Thank you. Please provide a short snippet as an example.
>
>Neil
>PS Do you need a unique ID if you are only reading the data with no intention of writing data to the view?
>
>>Without primary key you will be not able to update properly. AFAIK, the Glen' idea to use recn() does not work. I would use SQL update command in this case.
>>
>>
>>
>>>Hi Glenn,
>>>
>>>I have been making plans to proceed with your suggested solution. I have a potential problem. Back in the old fpw2.6 days, I did not include a unique identifier field in my data tables ie: cID or iID.
>>>Will this be a problem if I am attempting to hook into my fpw2.6 tables via updatable, parameterized views?
>>>
>>>Neil