Open Table results:Decimal's precision is too small...

[Phil]

Another Decimal issue. I an unable to toucv this table, which resides
in MYSQL.

Just attempting to open it in table view, much less use it in query,
results in this stupid BS error. Is there anyway around this?

Phil

 

[Tom Ellison]

Dear Phil:

Since no one else has tackled this, I though I might offer a theory.

Perhaps the table contains some datatype that cannot be rendered by Access.
If this is conceivable, you might just experiement with making a copy of
this table and removing all the columns of each type, one type at a time,
till the error goes away. At least you would learn what is causing this.
If you do find out what it is, you may be able to create a new column of
another type and move the data into it within MySQL, then try importing
again.

If this isn't helpful, well, just consider what it cost you! Sorry, that's
my best guess and advice.

Tom Ellison

 

[Phil]

I am not sure I can muck around with table. At the very least it woudl
be a sales job to the Vendor/programmer of the application. However,
knowing exactly which field or fields is causing the problem woudl make
the sales job easier, so it is not bad advice. Thanx a lot.

 

[Phil]

Well, we figured it out. Figured I may as well let you know in case you
run into it again.

Field in MYSQL was configured for Decimal 4,4 which means 4 digits on
either side of the decimal. The data in the first record, (and a whole
bunch of others,) was 5 digits to the left, and 2 to the right. MYSQL,
at least the version we are running, does not seem to care, but Access
throws a hissy. I guess the newest version of MYSQl, (which we are
going to upgrade to in a couple of months,) would also choke on it, so
it is better we found it now. Changed the datatype to decimal 16,4, and
all is right with the world.

Thanks

Phil