>Dear Hilmar,
>
>is this a good practice to replace all the tableupdate(.t.) statment in my project with the evaluation program segments as you have told me in the last thread to me, which writen as a procedure at stored procedure of the DBC. While in every instance I am about to save the change, the procedure is called to check whether it is conflict or not - > Save all or nothing ??
>
>With regards,
>
>Ransome

Well, I think Iwould place code on the form level. Try with one form first. If the form works well, copy the code to your form class. You do have one, I hope.

Well, the idea is something like this: you create a class from which all of your forms are derived. Any change made to this class will affect all of your forms.

Using a good framework will take many of your troubles away: these things are already solved there. Many frameworks cost around US$ 500, but I think cheaper frameworks are available as well (the CodeBook, I think, costs around US$ 50; it is one of the pioneers in the development of frameworks).

I wouldn't be too surprised if some freeware framework is available, as well, but I don't actually know of any.

Hilmar.