>>>>>Hello all. I am currently re-writing some legacy VFP apps into .NET web applications.
>>>>>My current problem exists with migrating over legacy data into SQL server.
>>>>>Most of these tables use character based prime keys, and are auto-incremented with the MM newid function using IncrementBase36.
>>>>>
>>>>>Since these prime keys are deployed into user data, there is no easy way to completely eliminate them until they are gradually phased out. As such, I am trying to use both a new integer based system and replicate any necessary legacy structure in SQL Server. Has anyone had any experience with writing a new equivalent for IncrementBase36?
>>>>>Thanks.
>>>>
>>>>Have you tried using uniqueidentifier?
>>>
>>>
>>>I thought uniqueidentifier only returned a 16 digit GUID. I need to increment an existing range - example 00001A to 00001B.
>>
>>I see. Perhaps you may need to roll your own unless someone already done it.
>
>Would this be a scalar function that I would trigger upon inserts?

Yes, I guess you can implement your own 'NewID() analogue' and put it into default value for the column.