>>I fixed the first problem. Although the second it happens on any field. I am taking the view and putting that into a grid. When I close my form and re-enter this is happening.
>>
>>3. I thought with a view you did not have to use data buffering?
>>
>>One more question, the view is paramterized view, I am testing this using the same data, It appears when I make the selection that the select statement of the view is not going back to the table and getting any information that has changed on that customer. So for example I can make a change exit the form, come back into the form select the same data, the change will appear in the grid, but that is not what is in the table. If I change something in the table, It will not update either, the only way I can get this to work right is change the name of the view that is created every time. Any Ideas on this problem?
>>
>>
>>Thank you
>>
>>Holly Clawson
>
>Holly -
>
>These views confused me at first, but i'm gettin the hang of them now and the learning curve is worth it -
>Yes, views are by nature data buffered. But this is cool, especially in a multiuser environment. You must first go into the view designer on the update criteria page and make sure that Send Sql Updates is checked. Then make sure that you have a unique field listed as the key. This should probable be marked non updateable. Then check all the fields that you want to be able to update.
>
>Issuing a Requery() will load the database records into your view. When you have Row Buffering, moving the cursor off the record will save the data. When Table Buffering is on, you should issue Tableupdate() to dave your data. You can check the return value form TableUpdate() to see if the database actuallly was updated.
>
>One Note - when Row Buffering is on, and you edit the record and don't change records, the data is not updated. A Tableupdate here will make sure the data is saved. I ran into this leaving a form and the latest data was never saved...
>
>Good Luck...
>
>Jack


Jack,

I have a problem with my keyfield. I am using a parameterized view, that is created programmatically. I am getting an error when making a change and moving to a new field on the view. The error is that the key defined by the keyfield property for (tableName) is not unique. In the table I have an index set up on custno + locno + date. In the view I have :
dbsetprop('view_customer_rate.custno', 'field', 'keyfield', .t.)
dbsetprop('view_customer_rate.locno', 'field', 'keyfield', .t.)
dbsetprop('view_customer_rate.effdate', 'field', 'keyfield', .t.)
It sure looks to me like I have defined my keyfield in the table and the view. What Have I done wrong?

Thank you

Holly Clawson