If you want to use ADO, I would suggest using a double type. I am not sure I understand the thinking behind swapping the size/datatype. If you need to enforce things - consider creating a field rule - or - a middle tier item for holding a business rule.
>Thanks for this answer.
>Does this mean I need to enforce the maximum number of digits before the decimals i an other way? With a double I can't say it's a 5.2 (like a Numeric).
>What I do now is Stretch the numeric fields by 1 digit (alter table) before creating the recordset and shrinking it back after the recordset is ready processing. I could change this into making the field a Double and reset it to Numeric after processing but It's not the method I'd like to keep using. Any comments on enforcing the max digits with a double?
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only