:[EMAIL PROTECTED] On Behalf Of David Tod Sigafoos
Sent: Tuesday, 29 March 2005 2:49 AM
To: Ray Wurlod
Cc: u2-users@listserver.u2ug.org
Subject: Re[2]: [U2] BCI and Dates to SqlServer
Ray,
sorry to do this again but i forgot to mention ..
if i change the 'prepare' section as noted here .. it does
Ray,
if you get a chance could you please look at the sample code I sent.
I can not find any errors in it and yet the dates do not work.
According to the manual ..
If you use SQL.B.INTDATE, the SQL Client Interface assumes the program
variable holds a date in UniVerse internal date format and
Ray,
sorry to do this again but i forgot to mention ..
if i change the 'prepare' section as noted here .. it does work well.
Now I can modify the read, write shells to force the conversion ..
but now am really interested in why i am not getting it right to
begin with g
*if
Can you re-send the sample code? I seem to have deleted it already.
Thanks,
Ray
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
What happens if you replace SQL.B.INTDATE with SQL.B.BASIC in the
SQLBindParameter call?
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Ray,
Thursday, March 24, 2005, 1:52:39 PM, you wrote:
RW BCI mimics the ODBC API, so dates are expected to be in ODBC format
(-MM-DD).
yes ..
RW Using the constant SQL.B.DATE in SQLBindParameter() or
RW SQLBindColumn() causes an implicit conversion to occur, so that
RW you get internal
Ray,
Thursday, March 24, 2005, 1:52:39 PM, you wrote:
snip
as further follow up here is a sample routine and info. Note that
that the only problem shows up after the sqlExecute .. and it is
caused by the write ..
RUN DAVES.BP DATE_TEST.MV
