Today, when a ODBC connection is lost, we get:
(For SQL server)
A SQL server login screen which (in my opinion) the user should never see in the first place. He has no idea what to with it.
When/if he cancels, he gets an ugly error message.
We need to be able to:
A) Handle that failure gracefully WITHOUT showing the login screen.
A++) Be able to reconnect without having to restart the application.198 votes
This has been fixed and released in recent Access builds.
When in tabbed View, it would be nice to be able to drag tabs to rearrange them
thank you22 votes
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.125 votes
(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).
- Don't see your idea?