J
Jeroen Smits
I think I found a bug in .NET 1.1 using the OleDb classes
using:
..NET 1.1
Access MDB file (2000 format)
Localization set to Dutch (or probably any localization where the , is used
for decimal and . is used for thousands)
steps to reproduce problem:
Create a OleDbCommand with a sql statement like
INSERT INTO [TABLENAME] ( [DECIMALFIELDNAME] ) VALUES( ? )
Then use the Parameters.Add on the OleDbCommand to add a number for the ?
variable, that uses a decimal. For example 2.75m
After the insert executed the record appears as if no decimal sign was
there, in this case it would be 275 instead of 2.75
probable cause:
I think oledb (or access?) expects the value in local format, while
OldDbCommand.Parameters supplies the InvariantCulture version.
using:
..NET 1.1
Access MDB file (2000 format)
Localization set to Dutch (or probably any localization where the , is used
for decimal and . is used for thousands)
steps to reproduce problem:
Create a OleDbCommand with a sql statement like
INSERT INTO [TABLENAME] ( [DECIMALFIELDNAME] ) VALUES( ? )
Then use the Parameters.Add on the OleDbCommand to add a number for the ?
variable, that uses a decimal. For example 2.75m
After the insert executed the record appears as if no decimal sign was
there, in this case it would be 275 instead of 2.75
probable cause:
I think oledb (or access?) expects the value in local format, while
OldDbCommand.Parameters supplies the InvariantCulture version.