I have a table in SQL tblOrdOutput which holds an integer field. This field needs to contain decimals from now on, so I changed the field to "real" on SQL server. When I link the table directly, the field displays as numeric/single in Access.
There is a view that read info from this table directly, combining it with some other selects), like "select * from tblOrdOutput", this view is also linked to Access (to be used in some form)
So, in the Access linked table the field is now single. In the view the field remains Integer and displays decimal numbers as integer (so 1,1 becomes 1.0). The form is based on the view, so as soon as you put a decimal number in the field it's changed to integer after input.
I tried:
- refreshing the links
- reconnecting the links
- creating another linked table to the same view
Nothing makes the field in the linked view change to single in Access
The strange thing is, there is already another decimal field in the same table which is also set as real, and THIS field displays as single in both the linked table and the linked view.
The only difference between the fields is that the first allows NULL and the second doens't. Changing this also doesn't help.
Anyone?
Maybe I should add that this Access application has been converted from ADP to ACCDB last year (because O365). I converted it, but I did not develop the ADP (it's been in use as an ADP for some 13 years now, since last year as an accdb)
There is a view that read info from this table directly, combining it with some other selects), like "select * from tblOrdOutput", this view is also linked to Access (to be used in some form)
So, in the Access linked table the field is now single. In the view the field remains Integer and displays decimal numbers as integer (so 1,1 becomes 1.0). The form is based on the view, so as soon as you put a decimal number in the field it's changed to integer after input.
I tried:
- refreshing the links
- reconnecting the links
- creating another linked table to the same view
Nothing makes the field in the linked view change to single in Access
The strange thing is, there is already another decimal field in the same table which is also set as real, and THIS field displays as single in both the linked table and the linked view.
The only difference between the fields is that the first allows NULL and the second doens't. Changing this also doesn't help.
Anyone?
Maybe I should add that this Access application has been converted from ADP to ACCDB last year (because O365). I converted it, but I did not develop the ADP (it's been in use as an ADP for some 13 years now, since last year as an accdb)