Skip to Content
author's profile photo Former Member
Former Member

Crystal Designer is not recognizing CLR based Stored Procedures

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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on Oct 30, 2010 at 07:59 PM

    Correct, CR doesn't support those.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 29, 2010 at 10:36 PM

    My workaround for the time being is to create a normal Transact SQL stored procedure which calls the CLR based stored procedure.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.