Subject | RE: [firebird-support] Connecting with ODBC - Need a trigger on SELECT??? |
---|---|
Author | Michael L. Horne |
Post date | 2005-04-07T20:34:58Z |
I had hoped that I could write my own sql to supply
results to the program but it doesn't allow that.
It tries to do all the work its self. First it shows
a list of the files and views for you to pick from
then a list of the fields in the file you chose.
So there is no way currently to have it pick a
stored procedure. I was hoping that someone would
have a trick?
Thanks
results to the program but it doesn't allow that.
It tries to do all the work its self. First it shows
a list of the files and views for you to pick from
then a list of the fields in the file you chose.
So there is no way currently to have it pick a
stored procedure. I was hoping that someone would
have a trick?
Thanks
> -----Original Message-----
> From: Alan McDonald [mailto:alan@...]
> Sent: Wednesday, April 06, 2005 5:40 PM
> To: firebird-support@yahoogroups.com
> Subject: RE: [firebird-support] Connecting with ODBC - Need a
> trigger on SELECT???
>
>
> do you use SELECT from SP? or EXECUTE?
> If it's a selectable SP. use SELECT
> Alan
>
>
>
> >
> > Hello,
> >
> > I am connecting to Firebird from a program with ODBC.
> >
> > In the program it allows me to select from tables and views
> > but not Stored Procedures and match the fields in those
> > tables up to the programs fields.
> >
> > The program seems to be limited in that it expects
> > a flat file of shipping info with all the addresses, ...
> > for a package in a single record. We don't store it that
> > way.
> >
> > The program I am trying to setup is UPS WorldShip and
> > I can get it to connect and pull data, just as things
> > are I will be forced to create another file and update
> > it every time the order records are changed.
> >
> > So, I was wondering if there is a way where I could fire
> > a trigger on a select? Or trick ODBC into reporting a
> > stored procedure as a file? Or does anyone have another
> > suggestion?
> >
> > Thanks
> > Michael L. Horne