I think I understand your reasoning. By using an SP I can also allow for parameters to be passed giving the user more flexibilty. In addition, the SP...

In this particular instance use of the View is for reporting only. For integrity purposes, many of my tables columns store identity keys to actual data records in...

I'll check that. What I am trying to figure out is how is the ERR.Description being built. Consider the following:

UPDATE statement conflicted with COLUMN CHECK constraint 'CK_Region'. The...

Are you kidding? That would make sense 😉

Expediancy is the primary reason I haven't gone this route as yet. My current routines are already debugged and working so...

Hi,

Here is the SP. Again, all I want the SP to do is set the identity property off to allow a subsequent ADO .AddNew method to insert a record...

Hi,

Thanks, that got me moving forward. I'm now using it in my VB code. In this instance, I'm using the VB data Environment and the Command Object point...

Hi,

I'm missing something... Here is my SP.

CREATE PROCEDURE [Set_Fran_Id]

AS

SELECT *

FROM [Catv2].[dbo].[NewFranchise]

GO

SET IDENTITY_INSERT [Catv2].[dbo].[NewFranchise]

GO

The syntax checks but after I save it the Set statement is dropped from the...