>Hi Tim,
>
>Thanks for the info. However, I do not have the windows solution that you mentioned.

I was just referring to the Mere Mortals solution for Windows Forms. If Mere Mortals is installed, you can open that solution by navigating to Program Files \Mere Mortals .NET Framework 2008 \Mere Mortals Framework Winodws Forms \ Mere Mortals Framework Windows Forms.sln
Once this solution is opened you can easily look at the code for the framework to see how specific things work. In this case if you look at the form save method you will know what is happening. Then if you decide to override this method in your own solution classes, you know what was originally in there. I don't recommend changing the framework code directly.

Also, in order to minimize the changes of source code, we have renamed the original table to a different name and the XP_CRYPT will automatically create a view with the original table name. We have no problem on the existing select function, except the BO.Save method, which the encrypted field will have the read-only error.

Did you run the business Object Generator to create your business objects based on this new view rather than the table?
In order to figure out which part is causing you this read-only error (probably because of the View) I recommend that you add the debug symbols to your project for the Mere Mortals references and then set a breakpoint in the Save method and step through to find out what you can do to get around it. Check out the Dev Guide section "Stepping through MM .NET Code in the Debugger" under Advanced Topics down toward the bottom.
>
>Kindly advise, thanks.

I hope that helps, if you need further info, please ask.
Tim