Not really. But I really don't need it in my applications since I already have a very solid routine to generate order numbers and so on. Also I was a little put off the first time I added an autoinc field. I do a lot of data handling via browse, and the "Field xx is read-only" message when I want to add a record by ctrl-y makes it impossible to use in many situations. Especially since I usually don't look at the screen all the time, and don't see the error message immediately.

>Any special reason why you're not using autoinc fields?
>
>>Hi Cesar,
>>
>>I'm sorry, but I really don't know since I don't use the autoinc field myself.
>>
>>>Hi Tore,
>>>
>>>I've been using Craig Berntson's tip for some years with success.
>>>But I still never used the Autoinc Integer fields.
>>>
>>>Is there a difference in security from one way to the other ?
>>>I'm using the native DBC
>>>
>>>TIA
>>>
>>>Cesar
>>>
>>>
>>>
>>>>>would you not be better of making code an integer(autoinc) field?
>>>>>
>>>>>How can I do it ?
>>>>>
>>>>>if this is a multi user app is there not a (very small) risk of two people updating the table at the same time and getting the same code value ?
>>>>>
>>>>>Yes it's an application that might have up to 5 computer in a network
>>>>>Is there any risk ?
>>>>
>>>>Yes, there's a huge risk, and it's no easy task to overcome. Read here for a solution: http://www.craigberntson.com/Articles/kb006.htm