Re: CREATE PROCEDURE

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

What you assume is not what I'm seeing. We use Crystal 8.5 for our products 
(I said 7 below - was incorrect.)

As I described, when I want to create a new report, a Data Explorer appears.
This has a list of connection types, including ODBC.
Opening that item (click the "+") displays a list of ODBC data sources 
defined on your machine.
They all have a "+", so they can be opened, as in Win Explorer.
When opened, what is shown are 2 categories - Tables and Stored Procedures, 
each with another "+" sign.
Opening the Stored Procedures item gives you a list of all stored 
procedures available to you, probably according to library list.
Selecting a stored procedure and clicking on the Add button puts that 
stored procedure into the report.
Bringing up the Field Explorer, the stored procedure appears under the 
Database Fields section.
Opening up the stored procedure displays a list of the fields available 
from the result set (or sets) that are defined in that stored procedure.

So Crystal treats stored procedures just like tables, since each produce 
result sets with identifiable fields. Crystal does the low-level stuff 
needed to get this information. And it makes the appropriate call, as 
needed. All in all, very handy and easy.

Cheers

Vern

At 11:46 AM 2/21/2003 -0600, you wrote:
> It does use *SQL naming. I'm not aware of a way to change that, but that 
> doesn't mean there isn't one. Afaik, result set columns are not published 
> anywhere. The definitions need to be retrieved by the client when the 
> result set is active. Return parameter values however, are an entirely 
> different matter. They are part of the procedure's call template, and 
> would be available to Crystal at design time. I suspect that in order to 
> use a stored procedure with Crystal, you'll need to base the report on a 
> crystal query, and use that to call the procedure. I haven't battled with 
> Crystal for several years though.
>
> At 19:04 02/20/2003, Vern Hamberg wrote:
> > Just for fun, this looks like *SQL naming syntax. Is it possible your 
> > ODBC data source wants *SYS syntax?
> >
> > As far as the message goes, it does look like a file-related matter. But 
> > Crystal might not care - it displays the fields from one of my stored 
> > procedures, in the "Database fields" section of the field browser. Go figure.
> >
> > Vern