Hi Cesar,

That's the reason I asked Tore. I thought that maybe he'd give me a reason like that. I'm wondering if the majority of VFP developers use it. And if not why.

>Hi Denis,
>
>Before I bought VFP9 I was using VFP7, that did not include this feature.
>
>At this moment, I'm not sure if I should keep using the good and old way or use the AUTOINC fields... My main doubt is that it is possible that I convert my DBC to SQL server, and I don't know which approach will offer me the easiest way to upsize my DBCs.
>
>Cesar
>
>
>
>>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