From the article: Microsoft Access 2010: What's Coming with Office 2010?
Microsoft announced yesterday that the next release of the Office suite will occur in 2010. News out of Redmond indicates that this release will place a heavy emphasis on web services. So far, there aren't any specific details available on what this means for Microsoft Access. What do you want to see in Access 2010? Share Your Ideas
Autoatic resizing for screen resolution
- DB forms were desigtned for 800x720 vs new 1670x1050 res. Current fix for type & form size is to create 116 DPI setting.
- —Guest tim herty
Access 2003 menus
- It is the menu style of 2007 that has stopped us moving to 2007 at work, if 2010 can not support the 2003 menu style, then we we have to serious consider the options and even look at non Microsoft development systems.
- —Guest Malcolm
Ability to crunch larger databases
- I would love to be able to apply the simplicity of the MS Access program to very large databases (2 GB +).
- —Guest Brian Corrigan
.net!
- Better integration to .net, or maybe just allow us to export all of access to .net so we don't have to use access anymore!
- —Guest Chris
Reports via email
- A wizard to send email reports to various recipients. For example, to send out class rosters to faculty via email. Each roster would have an email address that it would be sent to.
- —Guest Jerry Garcia
HATE new interface!!!!!
- PLEASE allow developers to choose to work with Access 2003 interface -- 2007 is obviously not meant for experienced access developers but rather new users
- —Guest terrycoco280
Student
- Hope that Microsoft Access 2010 can build an executable file that most of Access users are waiting for
- —Guest Rob Dy
Access Improvement Recommendations
- 1 - Kill the ribbon - most on this board are suggesting that... 2 - Allow developers to convert MDB/ACCDB to EXECUTABLES - it has been suggested a million times by users all over the world and yet there still is no ability to do so.... 3 - Bring the database window back....it's so obvious that what is currently available (2007) is NOT working for many users and/or developers... 4 - Increase security in MS Access - while I applaud the open format of the Access architecture, allow tables to be locked and not directly opened, increase security capabilities, and allow users to EASILY (meaning a drop-down option or code option) to encrypt data in tables 5 - Increase the table capacity to much larger than 4GB! What about 50GB? 6 - How about INCREASING the number of controls available in the dev tool box? The current toolbox is sparsely lacking in form controls - if you don't want the product to compete with VS, then create an add-in of some sort for Access
- —Guest Brice RIchard
What I want to see in Access 2010
- Easy Integration with SQL SERVER and more support with sharepoint server.
- —Guest Daniel
QBE & Query/Table portability to SQL
- QBE is way better in SSMS and Creating queries are way faster in SSMS than Access currently. Allow easy SQL code query development portablity to SQL server. Use standard SQL Table Creation definitions for ownership, use SQL Syntax as much as possible. I had to convert an Access database to SQL server code to design a data warehouse enterprise ETL solution and reports.. but it was so difficult and time consuming. Access was my development platform, to give the ETL developers what they needed to solve my larger problem once. I Had to convert all the code directly to SQL by hand. Access Query (SQL code) and proprietary expressions are fine, but they are too hard to get right most of the time or and do port to SQL code very well. I should be able to copy and paste into SSMS or some other BI tool. All standard T-SQL functions as expressions and syntax and provide a code conversion wizard for reuse. That would save lots of time. Make it easy to create tables as in SSMS.
- —dalejrstwin
Overhaul the IDE tool to VS/SSMS
- Since Access is the worst of the Office Apps and so Outdated: I would like to see Access IDE adopt most of the Visual Studio Developer IDE and SQL Server Management and Business Intelligence Tools/Interface. And drop the Ribbon. It gets in the way more often on smaller screens. Drop the new Database Objects window, takes up too much real-estate in its current form. I would also like to see SQL like SQL Server for individual objects like tables and as a whole database for end users. I would like to get rid of the proprietary SQL code developer and use the standard SQL compiler/syntax. I would allow forms be created like VS, and Reports like SQL Server Reporting Services as well. The current Access IDE is very outdated and archaic, and it takes forever to develop basic functionality found on a real system.. This would as allow better integration/portability to move between an Access DB solution and (called some new ACSQLDB file) and standard SQL Server tools. -Thanks MS Office
- —dalejrstwin
Remove changes that don't work
- I'm not the type of user who complains about changes just because they are unfamiliar, and I've given the ribbon bar and other changes a fair shake, and have gotten used to most of them. However, there are two new items in Access 2007 that simply don't work as well as their 2003 counterparts, and I'd like to see them changed in 2010. The first is the replacement for the database window. It just doesn't work if you have a large number of objects. The database window should return. The second is the sorting and group form for reports. It's incredibly tedious, requies too much clicking and searching to find the setting you want to change, and makes it too easy to accidenty delete a section. The 2003 equivalent was simple and elegant and allowed me to configure the report very quickly.
- —Guest Hubbity Bubba
Visual Studio integration
- Allow Forms and Reports to be created in Visual Studio
- —Guest guest
ms access 2010
- i would like to see the following 1. in the ADP full competability with sql 2008/10 2. service oriented 3. vba.net of some kind 4. ability to use vb.net objects in ms access forms 5. direct SQL statments asigned to local variable 6. ability to use adox in the application
- —Guest Daniel Chen
Fix the ADPs
- In Access 2007, adps felt fundamentally broken. Minor improvements were made, but in the end, they were just infuriating to work with. They were absurdly slow vs. Management Studio or ODBC, if you lose the db connection, you get an infinite "Connection Failure" error that makes you kill Access, and when you build a report/form based on a custom SQL statement, Access takes forever to constantly refresh the fields so it becomes nearly impossible to get things done... and of course there are so many more... Ultimately, adps were a real disaster. That's a shame because it's nice to be able to use Access as a simple forms took to manage a database. Please revist ADPs - fundamentally.
- —Guest Mike
1-15 of 24Next
