I have a maintenance form. All data operations (update/insert/delete) used to work great, until I decided to handle inserts through a stored procedure.

Well, it's still kind of works, but after new row is added and Save is clicked, BO state remains dirty no matter what. So when form is closing "Would you like to save changes" dialog is displayed, even though user did click save before (many times).

Another thing I am noticing is that BO always sees new row as "New" even after Save is clicked and changes committed to the db, so if user clicks save multiple times it keeps adding the same record over and over again.

Please help. Thank you.

>> Don't know if you looked at the DDT very much, but the SMO approach to schema changes - and the ability to easily add that into the app ala Stonefield update is pretty impressive.  <<

< rof,l > and < lol >!!!! With Andy's involvement in this project as DBA, you can well imagine that his reastion would be "over my dead body!". When we were watching things in SQL Profiler, he was very upset at seeing the framework make direct calls to SP_ExecuteSQL.

Hi Marcia,

Like in everything else, there are many ways to skin the cat, and once you get to know the tools available for SF (BOM,  DDT, RBS) and use them then you will see the light at the end of the tunnel These tools are design with automation in mind, so the application can take care of itself automatically or with your assistance but being easy on your part.   Please don't show this post to Andy