Importing from a package file


Author
Message
StrataFrame Team
S
StrataFrame Developer (6.2K reputation)StrataFrame Developer (6.2K reputation)StrataFrame Developer (6.2K reputation)StrataFrame Developer (6.2K reputation)StrataFrame Developer (6.2K reputation)StrataFrame Developer (6.2K reputation)StrataFrame Developer (6.2K reputation)StrataFrame Developer (6.2K reputation)StrataFrame Developer (6.2K reputation)
Group: StrataFrame Developers
Posts: 3K, Visits: 2.5K
When we create the package file, we generate that code... it should be removed when re-importing it back in.  Thanks for the notice.
Keith Chisarik
Keith Chisarik
StrataFrame VIP (2.2K reputation)StrataFrame VIP (2.2K reputation)StrataFrame VIP (2.2K reputation)StrataFrame VIP (2.2K reputation)StrataFrame VIP (2.2K reputation)StrataFrame VIP (2.2K reputation)StrataFrame VIP (2.2K reputation)StrataFrame VIP (2.2K reputation)StrataFrame VIP (2.2K reputation)
Group: StrataFrame Users
Posts: 939, Visits: 40K
When importing a DDT project from a package file it seems that unwanted syntax is added to the CREATE PROCEDURE area.



It adds the following which I have had to delete from 50+ stored procs......am I missing something?



IF EXISTS(SELECT [name] FROM [sysobjects] WHERE [name] = 'aspnet_CheckSchemaVersion')

DROP PROCEDURE [dbo].[aspnet_CheckSchemaVersion]

GO

set ANSI_NULLS ON

set QUOTED_IDENTIFIER ON

GO -----> already added in the 'Pre-Create/Environment Code area



CREATE PROCEDURE [dbo].[aspnet_CheckSchemaVersion] ----> Added via the tool



It also throws up on the "IF EXISTS...." line, is this misplaced as well?




Keith Chisarik
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search