Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Forcing RLOCK() in SQL Server
Message
 
 
To
20/11/2005 21:40:49
General information
Forum:
Visual FoxPro
Category:
Databases,Tables, Views, Indexing and SQL syntax
Miscellaneous
Thread ID:
01070653
Message ID:
01070671
Views:
16
>If we have the numeric IDENTIFY column with NEWID() defined, is there a use to use the stored procedure, as defined in the other message, to obtain the next ID?

The numeric IDENTIFY column doesn't require any additional functions to generate next ID. The uniqueidentifier column (UUID) can use NEWID() as default value.


>The function I am using was developed before VFP supported that. It was never changed when it became available natively in the table. If I would design it from the beginning, I would use the automatic approach supported by the product. Basically, we have the same ability in SQL Server. So, I am wondering why doing it manually would serve for.

I use IDENTITY in all new development. I may use "manual" approach for compatibility with some existing system.
--sb--
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform