Re: CREATE PROCEDURE

[Vern Hamberg <vhamberg@xxxxxxxxxxxxxxxxxxxxxxxxx>]

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/