AutoInc doesn't work on a view. It works on the actual table. Skipped values are inconsequential as they are only used by the system. But, if the user cancels, it's before the process of inserting a record, so it shouldn't matter anyway.

>I heard that it's a bad idea to use that, so I haven't. I don't remember who/what/where I heard not to use that - but it seems like I remember playing around with it and there was some issue if a user wanted to cancel an action - it was skipping the next value...I could be wrong about that. Now I know for sure AutoInc does not work with remote views - and based on what you're saying I'm guessing that this DOES work with local views. Anyway even if I ran across a VFP app that used this I would just change it in the VFP table and be done with it. Still end up a lot less hassle than all the other jazz I'd have to do. One thing I do not know is what the advantages of using AutoInc are other than saving a line or two of code and keeping track of keys yourself.