Subject | Re: Problem with stored procure and Crystal reports |
---|---|
Author | diegodelafuente |
Post date | 2011-06-09T17:49:05Z |
People.
I tried using the new ODBC driver and CR could get access to the DB and populate the report using the stored procedures.
So, the issue is with the oledb connector.
It is a big problem for me cos I will not drop it and replace with a different connector.
The idea is launch reports from the App. I'm thinking to use only the ODBC driver to launch reports.
I will look for an unpdated oledb driver, to check if there is a know solved issue with my oledb driver.
Thanks and regards
I tried using the new ODBC driver and CR could get access to the DB and populate the report using the stored procedures.
So, the issue is with the oledb connector.
It is a big problem for me cos I will not drop it and replace with a different connector.
The idea is launch reports from the App. I'm thinking to use only the ODBC driver to launch reports.
I will look for an unpdated oledb driver, to check if there is a know solved issue with my oledb driver.
Thanks and regards
--- In firebird-support@yahoogroups.com, Roger Vellacott <rvellacott@...> wrote:
>
> --- In firebird-support@yahoogroups.com, André Knappstein, Controlling <Knappstein@> wrote:
> >
> > d> for select versioncol,
> > d> fechaactualizacion
> > d> from actualizaciones
> > d> into :versioncol,
> > d> :fechaactualizacion
> > d> do
> > d> begin
> > d> suspend;
> > d> end
> >
> > And for what it's worth I'd have a bad feeling about using identical names for output parameters and the column names. I can't explain why, but I'd just not do it :)
> >
>
> I do it all the time. I am sure there is absolutely no problem in having columns putting their values into variables of the same name as the column.
>
> Roger Vellacott
> Passfield Data Systems Ltd
>