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
(YYYY-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 format out of a SELECT, and must supply internal
RW> format in bound variables to an INSERT or UPDATE.
I do use the SQL.B.INTDATE and SQL.DATE. MsSql creates as datetime
(using Enterprise Manager) ..
As soon as i try to write to this column i get the error. If i change
the column to 'char' in all places then it writes out correctly.
It is only DATE that i have any problems with (haven't tried time).
INTs chars varchars (which map also to text columns) etc work well.
It is only date .. it must be something on my end as I would find it
odd that there is some ambiguity in the uv -> odbc interface
--
DSig `````
David Tod Sigafoos ( O O )
_______oOOo__( )__oOOo_______
Cannot open file "C:\DOCUMENTS AND SETTINGS\DAVID TOD SIGAFOOS\APPLICATION
DATA\BATMAIL\COOKIES.TXT"
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
