Anonymous
My feedback
-
6 votes
An error occurred while saving the comment -
25 votes
An error occurred while saving the comment Anonymous
commented
Let's dump macros altogether and just use VB only. Let's make Access itself smaller.
-
5 votes
An error occurred while saving the comment Anonymous
commented
This would make it more efficient to add read-only documents inside forms. For example, to add a tab with an End User License Agreement (200+ words) takes a lot of labels and text boxes, quickly filling up the form and taking huge amounts of storage. It'd be better to add a single HTML page from another source.
-
16 votes
An error occurred while saving the comment Anonymous
commented
SVG Image support would also help in making UWP/Fluent compliant interfaces.
-
10 votes
An error occurred while saving the comment Anonymous
commented
Agreed!
-
16 votes
An error occurred while saving the comment Anonymous
commented
I'm not sure how practical this really is, but if you go this route you might as well have Access build a Progressive Web App (PWA) that can run on anything.
-
25 votes
An error occurred while saving the comment Anonymous
commented
This should be a simple setting under "Current Database" in the options. Likewise, it should be easy to set the top/left corner and height/width of the form relative to the screen--not just inside the Access app.
-
7 votes
An error occurred while saving the comment Anonymous
commented
The Conditional Formatting in Excel is a good starting point. The UI there is a little confusing, but it's very powerful!
-
7 votes
An error occurred while saving the comment Anonymous
commented
Make this more like Visual Studio
-
130 votes
An error occurred while saving the comment Anonymous
commented
This also underscores my request for UWP/Fluent controls...
-
24 votes
An error occurred while saving the comment Anonymous
commented
This is a good idea, but I'd be happy with at least 2-3 user-definable properties that we can use for our own purposes. Right now, I use the .tag property for this, but it's kind of a kludge.
-
52 votesAnonymous
shared this idea
·
-
2 votesAnonymous
shared this idea
·
-
1 vote0 comments · Access (Desktop Application) » Automating Tasks · Flag idea as inappropriate… · Admin →Anonymous
shared this idea
·
-
1 voteAnonymous
shared this idea
·
-
310 votes
Thank you for your feedback.
In terms of setting SQL Server as the default database format, that is currently not in scope for the Access product. We have provided and will continue to provide efficient methods to integrate your Access data with SQL server, and the team will continue to develop more features that streamline the data migration experience (see https://support.office.com/en-us/article/migrate-an-access-database-to-sql-server-7bac0438-498a-4f53-b17b-cc22fc42c979)
However, the ACE database engine has and will continue to be Access’s central data storage unit.
There are new features coming soon that will improve the Access: SQL experience, and we are excited to share this news. Please stay tuned! :)
An error occurred while saving the comment Anonymous
commented
This should include supporting all SQL Server datatypes, the same SQL language, real SQL parameter support, rules, etc...
And don't stop there: match SQL Server terminology, like Views instead of Queries. If you take this far enough, you could dump both JET and ACE. That said, we don't want a copy of SQL Server added to the package.
Anonymous
supported this idea
·
-
1 voteAnonymous
shared this idea
·
-
4 votes2 comments · Access (Desktop Application) » Automating Tasks · Flag idea as inappropriate… · Admin →Anonymous
shared this idea
·
-
24 votes3 comments · Access (Desktop Application) » Automating Tasks · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
2 votesAnonymous
supported this idea
·
This is important for UWP/Fluent -like apps for Windows 10.