Hi Mel:

>Do you know of any other way to deal with this issue

Well, there are probably a bunch of ways to do this but not "automatically" with CM if you persist in using a view. I suppose it begs the question, why are you using a local view?

In my earliest VFP days, the logic and prevailing wizdom appeared to advocate the use of local views in preference to tables. There are a few good'ish reasons to use local views but with Codemine, the distinction is blurred somewhat. Once you have defined a cursor object, it is relatively trivial to change the cursor object's data source. So, you can easily use tables and then if you want to change to views later, then the cursor object provides the same "interface" to your forms and code with a simple change of data source. If you need the re-cycle deleted records feature of Codemine, then if you don't particularly need a local view, why not just directly use the table?

However, it must be said that after reading one of your other replies in this thread, it would seem like you are just sticking a band-aid over your PK problem. I have lots of CM code out there and have never had a single problem with PK generation. It might be better to try and find out why you are getting duplicate keys generated.