>>>>When I test that view in the project manager I'm able to save the changes made.
>>>>
>>>>When I want to update through my form I can't. I have an error message saying that "the key columns for the update table is not specified". The view is marked as updateable, The primary key field is defined and the field that does'nt want to be updated is defined also as updateable.
>>>>
>>>>That view was not made with the view designer. I used ViewEdit to do it. I also have eView and Stonefield Database Toolkit. Everything looks good to me when using all of these tools.
>>>>
>>>>Anybody have a clue on this one?
>>>
>>>Forget about that problem I found the solution.
>>
>>Denis,
>>
>>What was the solution?
>
>I did'nt give it because I don't really understand why what I did fixed it.
>
>Here's the thing.
>
>I added a field to a table and after that modified the view. In the form I copied a checkbox and redefined the control source and everything else. After that I was'nt able to save the modified data.
>
>At that point I redid the view I double-checked everything but still it was not working. As a last hope I deleted the (newly copied) checkbox from the form and added a checkbox by dragging and dropping from the toolbar. I then initialized all that was needed for that checkbox and tadaaa it worked.
>
>Can you explain this to me?

Denis;

This may or may not be similar to the problem you expressed. When using a data environment on the form rather than opening a table and selecting it, I have seen this type of performance. In VFP 3 it was very bad, VP 5 better and VFP 6 not too frequent. It seems that adding a field and recreating an associated view would sometimes get the view out of sync with the data environment of the form. With VFP 3 and 5, I would delete the data environment and drop it on the form again. With VFP 6 it will normally “cure itself” after opening and closing the form.

At any rate VFP can be interesting!

Tom