Community
Showing results for 
Search instead for 
Do you mean 
Reply

OLEDB2 Act_Columns.DecimalPrecision

Copper Contributor
Posts: 31
Country: USA

OLEDB2 Act_Columns.DecimalPrecision

Hello,

 

It looks like this field is defined as a varchar, is that how it was meant to be set up? For example, I have a few custom ACT! fields set as 2 places to the right of the decimal. These fields have an ascii 2 (not the string "2") as the content of the decimalprecision field. I would've expected this field to be an int, like the Act_Columns.Length field.

 

- Rob

Copper Super Contributor
Posts: 138
Country: United States

Re: OLEDB2 Act_Columns.DecimalPrecision

Rob, this appears to be a defect.  I am able to repro...

 

I've created Defect #88569 to track this.

 

Thanks!

 

Bill Blakey
ACT! Development Team
Sage Software

New Member
Posts: 2
Country: United States

Re: OLEDB2 Act_Columns.DecimalPrecision

I am having a problem with the decimalprecision value and wanted to ask if this defect has been corrected or if there is a workaround.

 

Thanks,

Leslie

Nickel Elite Contributor
Posts: 937
Country: USA

Re: OLEDB2 Act_Columns.DecimalPrecision

Why not just cast it as the datatype you want in your SQL?
New Member
Posts: 2
Country: United States

Re: OLEDB2 Act_Columns.DecimalPrecision

I have tried to cast the fields as decimal but if the filed name contains spaces, this will not work.  I have tried to change the field names but the oledb2 does not update with the new names.  I have tried using ActDiag to rebuild the provider and still it does not reflect the new field names.  Oledb does reflect the new field names immediately after the change.  Any suggestions?