>All,
>
>The SETFLDSTATE command apparently does have some issues! Actually, it often does work just fine (as it's doing right now on my machine <g>).
>
>I'll be working with Bill this week, so I'll check into the problem further and report back with a solution.
>
>Regards,

Meantime, put the NEWID() function as default in your views. This makes the setfldstate unneccesary. (Normally NEWID will dectect your base table name, but in case it does not you can add your basetable name (all uppercase) as a parameter.


If you are updating two tables from a single view and they are in one to many relation -- only put NEWID in the many end. Add a single call to to Newid for the "one" side in the presave hook of your business object and replace all instances of the "one" key with the results.

This is assuming your view otherwise updates both halves of the relationship properly.