F
François Rioux
Hi,
I'm using VSStudio.Net 2003 bound to an Access 2000 DB. Using the datasets
and an oledb data adapter.
Using the DACW, I generate a dataadapter select and insert,update,delete
commands using the DACW. The Insert command parameter type for an Access
Date/Time field is DBDate, which results in troncated dates (no hours or
minutes) in the database upon insertion and updates of new rows from the
data adapter update method.
So if I fill the ds table, modify a row field and update the underlying
table results in a truncated date!
The oledb type corresponding to a datetime is DBTimestamp not DBDate, for
what I can read in the help (Using Parameters with a DataAdapter in the
..Net Framework User Guide). Manually changing the parameter type to
DBTimestamp solves this issue.
This looks to me like a bug, unless there is a clear explanation I can't
figure out.
Can some confirm this is a bug or indicate me how to correctly use the DACW
to generete update commands that work.
Thanks,
François.
I'm using VSStudio.Net 2003 bound to an Access 2000 DB. Using the datasets
and an oledb data adapter.
Using the DACW, I generate a dataadapter select and insert,update,delete
commands using the DACW. The Insert command parameter type for an Access
Date/Time field is DBDate, which results in troncated dates (no hours or
minutes) in the database upon insertion and updates of new rows from the
data adapter update method.
So if I fill the ds table, modify a row field and update the underlying
table results in a truncated date!
The oledb type corresponding to a datetime is DBTimestamp not DBDate, for
what I can read in the help (Using Parameters with a DataAdapter in the
..Net Framework User Guide). Manually changing the parameter type to
DBTimestamp solves this issue.
This looks to me like a bug, unless there is a clear explanation I can't
figure out.
Can some confirm this is a bug or indicate me how to correctly use the DACW
to generete update commands that work.
Thanks,
François.