DecimalPlaces Property

  • Thread starter Thread starter Terry Roberts
  • Start date Start date
T

Terry Roberts

I'm running into an unusual problem in A2K2 while creating
a table on a SQL Server 2K. When I attempt to open the
table in design mode, I get an information box that tells
me "The setting for the DecimalPlaces property must be
from 0 through 15, or 255 for Auto (Default)."

I've checked every field in the table, and none of them
have anything other than 0 in the decimal places property.
In fact, there are only three fields that have anything at
all in the decimal places property, and all of them are
SmallMoney fields.

I've check with the SQL newsgroup, and no one was able to
identify the source of the problem. I have tried breaking
and relinking all links to the table (through the Database
Diagram), and it didn't solve the problem. Any assistance
would be greatly appreciated.

TIA,

Terry Roberts
 
Just a guess, but, native Jet tables store superseded field characteristics
"behind the scenes" until the database has been compacted. Perhaps applies
to links as well. I'd try breaking the links, >compacting the (Jet)
database<, then re-establishing the links & trying again.

HTH,
TC
 
Terry,

You will find that one of the columns in the problematic table has an
'extended property' named 'MS_DecimalPlaces' and it should not,
probably due to a bug in Access that failed to remove this property
when you changed the columns datatype from one for which this property
makes sense.

You can see and edit or remove this property using MS' SQL Query
Analyzer. Open the 'object browser', navigate to each column, right
click on it and examine the 'extended properties'. Find the errant
property, delete it, and try again.

Good luck,

-Malcolm Cook
 
Back
Top