
Crystal report using SQL stored proc locks server!!
Check out the Crystal Print Engine API in the Developer Help file. If you're
running 32-bit: Crystal, VB, and Windows; you can use the Print Engine DLL to
run your reports and piggyback your VB ODBC connection. Maybe you can in 16-bit
too, I don't know, never done it in 16-bit.
I need to look at that 16-bit Print Engine API myself. I'm developing Crystal
5.0 reports that get their data by executing Sybase XI stored proc's I'm
writing. Someone else is writing the VB front-end. When I run the reports in
Crystal, they prompt me for the input parameters. I'm not sure how to pass them
from VB 4.0 16-bit, to Crystal Reports 5.0 Professional 16-bit. The users are
running on Windows 3.1 and Windows 95 systems.
I've used Formulas in the past to pass params from VB to Crystal, but I don't
know how to feed Crystal input params to use when it executes the stored procs.
Unfortunately, the VB programmer is new to VB and Crystal. And, I'm so busy
writing stored procs to denormalize the data from 5th-form normalized tables to
small report resultsets, and then developing the Crystal Reports, I just don't
have the time to play around with VB right now to figure it out.
If you could share any info on that, I'd sure appreciate it! If you know an
easy way to pass SP input params to Crystal using the OCX, that would be most
helpful, since the VB programmer is new and we have about a week left to finish
this project.
I was pulled into the project last week and handed 10 cross-tab reports to get
developed by this Friday, It wouldn't be so bad if someon hadn't insisted that
the database be designed with all the tables normalized to the 5th form. I'm
having to do lots of intermediate joins and data manipulation to piece the
report data together. My SP writing is sure getting a workout! :)
Regards,
John
Quote:
>I am using Crystal to make some dandy reports on the content of a MS SQL 6.5
>database. To accomplish this I am using a piggyback ODBC connection through
>an app connected to the sqlserver. It all looks supernice to my user, but
>everyone else is waiting.... The stored procedures are using SELECT INTO and
>I have set TRACEON(5302) to no awail. Have anyone else experienced this
>problem? Nice workarounds? Anyone =).
>/staffan