Changed size of DECIMAL column in SQL Server, Access doesn't accept it

[Thomasso]

Hello,



I had a DECIMAL(6,2) column created in SQL Server. When migrating data, I realized that this is too small, as I need to store values above 9999.99. Therefore, I altered the column to be DECIMAL(10,2):

https://i.imgur.com/aYAp3jy.png

The problem is that Access still consideres the linked views to be DECIMAL(6,2) and gives me the "precision errror".

https://i.imgur.com/NpvXfX0.png

I relinked the view, of course. Tried deleting it completely and linking again, as well as right click & update link.

Any ideas what I should do? Thank you very much.

Tomas

[Thomasso]

Okay, I will answer myself, if anyone comes across this issue. What helped was to drop and create the view itself on the SQL server. :-)

[Minty]

The explanation behind that is that the view will set a default datatype based on the underlying data when it's created.
The same can happen with Varchar() data type. If you created a field

'ShortText' as MyTxtField

Then linked to it in access you will see the datatype as ShortText with a field size of 9 and in SSMS look at the columns for the view and it will say Varchar(9)
Without altering and then saving the view, that setting will "stick".