Re: stored proc RETURN_VALUE.... there it is, I want to use it !!!

Hey... thanx!

When I tried using the parameter.refresh as you had suggested so that I
didn't have to createparameters, just assign values.. all seemed well until
I call 'open' and I got an exception on sqloledb.dll... any suggestions
there?

I had to go ahead and dump trying to use the refresh and go back to
createpara...

b
"Brian Bushay TeamB" <BBushay@xxxxxxxxx> wrote in message
news:eu0371hla6ugmlekgdnfch1mc5tnfflesq@xxxxxxxxxx
>
> >Brian... for some reason I can't seem to work with you
parameters.refresh...
> >when I use it I appear to assign the parameters properly... I thing,
please
> >correct me if I'm wrong.. but when I open the stored proc I get an nasty
> >exception on sqloledb.dll... strange thing is that it only happens the
> >second time and subsequent times.
> I don't understand what you are asking here
> >
> >Problem with my old and now much preferred method was, you won't believe
> >this, I'm having trouble with it... but, where the stored procedure was
> >defined with variables @meetingCode char(6), @guestID char(10) I could
not
> >create them in code 1. guestID and 2. meetingCode... have to create them
1.
> >meetingCode and 2. guestID. Ya!... what's up with that? when I switched
> >the order in which I was creating the 'named' parameters life is good,
sweet
> >and prosperous... if anyone can explain my anomolies, confusion and
> >misperception to me please have at it...
> Borland's ADO components handle parameters by position. Translating the
name of
> the parameter to its position in the Parameters. So you must create them
in the
> order that the StoredProc uses them.
> --
> Brian Bushay (TeamB)
> Bbushay@xxxxxxxxx


.