>Yes I've been using optimistic record locking in my applications, just was wondering how it works with views and if I'd need to make any changes on my programs.

One "change" is that your application will be really fast if you use p-views in a grid (as compared to a filtered table in a grid).

As to the changes you have to program - one thing that is different is that a view can have no permanent index. For instance, if a certain form has a statement like "SET ORDER TO ClientCode", you will have to change that. The view can already be ordered, but you can't SEEK - unless you create a temporary index after opening the view.

Some other things may change, too. The framework I use needs to detect the primary key for some tasks (e.g., show audit trail). It can't get the primary key for a view (of course not; a view has no permanent indices, and therefore no primary key).

You will have to do some adaptations for views.

But in general, I believe these changes will be much simpler than doing the updates yourself, through a cursor (your cursor doesn't have permanent indices nor a primary key either, nor does it initially allow SEEK, right?).

But in many cases, the view or p-view can be treated as just another table.

Hilmar.