Please make Access able to handle more data types as are commonly used in Server databases
For example Access cannot handle BigInt in linked tables. This has been in use in SQL Server for many years, but Access can't handle them in linked tables.
Alan Cossey
shared this idea
(Apologies for the irrelevant emailed response earlier)
Not too long ago we added support for Large Number (Big Int) – https://blogs.office.com/en-us/2017/03/06/new-in-access-2016-large-number-bigint-support/
We reviewed all the suggestions below and took note of them. I’m going to mark this topic as Done so you can your votes back.
If you’d like to ask for additional data type support, please create new suggestion (one for each).
Thanks,
Michal [MSFT]
31 comments
-
Alphonse Giambrone
commented
Date, Time, BigInt. Note though that support in tables is not so useful if there are not corresponding VBA data types.
-
Anders Ebro (TheSmileyCoder)
commented
GUID
Date
Time
BigInt -
Alan Cossey
commented
BigInt
Date
Time -
B. Clothier
commented
My preferred order:
Date
Time(x)
BigInt
XML
GUID
Datetime2(x) [esp. the subsecond support]The more esoteric data types such like spatial or hierarchy are nice to have but I can live without them.
-
Mark Burns
commented
@Anon... that would imply a larger database to hold those varbinary objects would it not? ...and they have already stated that they have no plans for giving us larger ACE database files.
-
caw78
commented
Handling Varbinary fields would make document management better
-
Anders Ebro (TheSmileyCoder)
commented
Aye, better GUID support.
-
George Hepworth
commented
I agree with Mark Burns.
-
Greg
commented
Better GUID support please!
-
Mark Burns
commented
Also, Native support in VBA and Ace for a BiGInt (or at least for 64-bit Integers) datatype would be another GREAT addition.
-
Crystal
commented
While Access can handle the Decimal data type in tables, VBA does not have a Decimal type, which would be nice to have as well so Decimal can be better taken advantage of.