Re: CREATE PROCEDURE

[Pete Hall <pbhall@xxxxxxxxxxxxx>]

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
>
> At 06:26 PM 2/20/2003 -0600, you wrote:
> > At 13:14 02/20/2003, Vern Hamberg wrote:
> > > Yeah, but the result set has fields. When I choose my ODBC source in 
> > > Crystal (ver 7) I see a list of stored procedures in a library, and this 
> > > is treated just like a table. Crystal will use the appropriate CALL to 
> > > execute it.
> > >
> > > > > 'Error opening file. There are no fields in the file: 
> > > > > "SYS.Lib.Proc(Test)".
> > > >
> > > > I think you're seeing that because a stored procedure is not a file. 
> > > > I've always needed to use the CALL command to execute a stored 
> > > > procedure via ODBC. You may also need to do it with a Crystal query. I 
> > > > don't remember.
> >
> >
> > The error message sure looks like it's trying to open a file, not execute 
> > a call. Have you tried running an ODBC trace to see what command Crystal 
> > is actually sending? Can you execute the stored procedure another way 
> > like with MSQuery?

Pete Hall
pbhall@xxxxxxxxxxxxx
http://www.pbhall.us/