Re: Re[2]: Stored procedure INOUT parm -- MIDRANGE-L

Yuck!!!! Why would anyone in this world use MS VC++!!!!

Yes if you are going to be programming to the ODBC API you will need to the
whole nasty process by hand. Honestly if your company wants the execution
time of C++ but does not want to spend all the development $ of C++ have
them evaluate Borland's Delphi or C++ builder. I can SMOKE any VB programmer
in coding a database program ( And of course VB programmers can SMOKE VC++
programmers to nearly the same degree).

Please note I do not work for Borland, nor have I ever worked for them, but
for all my consulting work I do I use Delphi as the PC tool of choice. I
evaluated just about every tool that was available ( because I did not want
to use Pascal ) but finally after spending $10k of my own money I relented
and bought Delphi. I was productive with the tool within 2 weeks and have
loved it ever since. Some of my clients require me to use VB and that is
their prerogative, but the Delphi programs I have written run better,
install easier and do not crash. VB is a whole other story, but hey if my
client wants to keep paying me over and over to fix their problems when
Microsoft buggers up a DLL or something like that, well all I can say is
spend your money like you want.

So sorry about the evangelism but I really do feel quite strongly about this
issue.
Eric

______________________________________________
Eric N. Wilson
President
Doulos Software & Computer Services
2913 N Alder St.
Tacoma WA 98407


----- Original Message -----
From: <eric.delong@pmsi-services.com>
To: <MIDRANGE-L@midrange.com>
Sent: Friday, May 19, 2000 1:07 PM
Subject: Re[2]: Stored procedure INOUT parm


>
>      MS Visual C++. Actually, I think I may have found the documentation
>      I needed. It seems we need to use SQLPrepare and SQLBindParameter
>      for both parm1 and parm2. My associate was trying to pass parm1 as
>      a character literal and bindParm for the second.
>
>      As usual, I got my part ready to test in about five minutes. He
>      says he'll be ready to try his part Monday (probably). :)
>
>      I sure am glad these PC programmers have all these productivity
>      tools to make their coding easier. Otherwise, I'd have to wait til
>      next month to test......
>
>      BTW, if I'm still chasing the wrong rabbit, please let me know.
>
>      thanks again...
>      eric.delong@pmsi-services.com
>
>
> ______________________________ Reply Separator
_________________________________
> Subject: Re: Stored procedure INOUT parm
> Author:  <MIDRANGE-L@midrange.com> at INET_WACO
> Date:    5/19/00 8:38 AM
>
>
> What language are you using? With Delphi just set the parameter to In/Out
> and then after the call do something like
>
> SomeVariable := StoredProc1.ParamByName('SomeParm').Value;
>
> VB with ADO requires a little more setup but in the end you reference the
> Parameter's value the same way.
>
> HTH
> Eric Wilson
> ______________________________________________
> Eric N. Wilson
> President
> Doulos Software & Computer Services
> 2913 N Alder St.
> Tacoma WA 98407
>
>
> ----- Original Message -----
> From: <eric.delong@pmsi-services.com>
> To: <midrange-l@midrange.com>
> Sent: Friday, May 19, 2000 8:34 AM
> Subject: Stored procedure INOUT parm
>
>
> >
> >      I've written a stored procedure in RPG4, and tried to pass back a
> >      return value as the second parm. We want a PC app to call this
> >      procedure via ODBC, but we can't figure out how to map the INOUT
> >      parm to a host variable in the PC app. Can someone point me in the
> >      right direction?
> >
> >      tia,
> >
> >      eric.delong@pmsi-services.com
> >
> >
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator:
> david@midrange.com
> > +---
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---
>
>
>
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
david@midrange.com
> +---

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---