Jim:

I'm having some challenges with Crystal right now, so I ran some tests from
SQL explorer using the Intersolv ODBC driver.

The first test simply calls a select stored procedure:

SELECT * FROM BANKBAL('06/07/2000')

The trace is sel.log.

The 2nd test calls an exec stored procedure:

Execute Procedure PostJE('1/1/1980',0,0,0)

The 4th param is a return param, but there's no way to do that in SQL
explorer so I just loaded a dummy value instead.

The trace is exe.log.

Hope this helps,

Dan



-----Original Message-----
From: Jim Starkey [mailto:jas@...]
Sent: Wednesday, June 07, 2000 2:45 PM
To: IB-Architect@egroups.com; 'IB-Architect@egroups.com'
Subject: RE: [IB-Architect] Select procedures


At 02:36 PM 6/7/00 -0700, Dan Palley wrote:

>My guess is that it's not passing SQL directly through, since it has some
>limitations on what type of query you can build (i.e. no joins).
>
>I'm not really sure how the internals of Crystal works, but I'd be happy to
>do an ODBC trace for you; what should I be loooking for?
>

Don't know. If I knew, the trace wouldn't be necessary.

The question is whether to translate "{ call foo }" into
"execute procedure foo" or "select * from foo".

Jim Starkey

------------------------------------------------------------------------
Wrox Wireless Developer Conference, Amsterdam, July 10-12. Choose from
40+ technical sessions covering application of WAP, XML, ASP, Java and
C++ to mobile computing. Early Bird registration - save �200 NOW!
http://click.egroups.com/1/4855/4/_/830676/_/960414414/
------------------------------------------------------------------------

To unsubscribe from this group, send an email to:
IB-Architect-unsubscribe@onelist.com





[Non-text portions of this message have been removed]