on 10-29-2010 11:14 PM
I am using Cystal Developer XI R2 and connecting to a SQL Database. In that SQL Database I have created a CLR based Stored Procedure. I notice that the Crystal Designer (at least by default) does not recognize stored procedures that are CLR based.
My first guess is the reason for this is that the xtype value (from sysobjects table) on this type of procedure is 'PC' instead of the normal 'P' for procedures. Is it possible the designer is only listing objects where xtype is 'P'?
Is there any way to fix this?
Any help is greatly appreciated.
Edited by: Ratinator on Oct 30, 2010 12:21 AM
Correct, CR doesn't support those.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My workaround for the time being is to create a normal Transact SQL stored procedure which calls the CLR based stored procedure.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.