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
One Time Deployment
- Write code only once and deploy in Windows or Web.
- —Guest name
Support for larger DB
- Nowadays you are frequently dealing with much larger quantaties of data than in the past. For that reason, the 4GB limmit should be removed and ofcourse 64bit is the way to go Louis
- —Guest Louis
.NET
- Hello, Personnaly I would like the option to migrate VBA, Forms and reports to .NET Louis
- —Guest Louis
Kill the Ribbon!
- Kill the Ribbon! Or let us turn it off!
- —Guest Skip Tracer
Rona Rose
- Nice to have: 1.Upgrade to adp/sql inbuilt as in version 2000 2.More tools and wizards. 3.Better help for running parameterized sql statements 4.Ability to convert the form to web form(at least html of it) 5.Ability to convert access database to sql by a wizard(re-mapping the datatypes):there are third party tools already. 6.Compare between versions wizard, showing only the differences 7.Sendobject to have ability to bulk email(we need it for the office use) 8.Better intellisence:like in VS2008, ability to suggest corrections 9.Give all info for the references:what each library is doing and for what tools what library; 10.More info for the compiled final version:I had VS2008 installed, but when I compile an Access 2003 database, it suddenly started to add additional references, why? 11.F1 help is pointing to a knowledgebase which is just for all Microsoft, has to be specific to Access only.
- —Guest Rona Rose
Kill the Ribbon!
- As an Access developer we've had to stick with Access 2003 because the Access 2007 Ribbon Bar was totally unworkable - just messed up the GUI. We would love to stick with Access and move to 2010 but that Ribbon Bar has gotta go! C'mon, guys, at least let us be able to switch it off in code. Please, please ...
- —Chris_Linx
Chris
- Get the forms in access directly exportable to either aspx files or some other web readable format. I have so many legacy format that I would like to be webonized that it would be spectacular if all of these forms could just be saved as a file and readable via a web server...
- —Guest Chris
DevExpress like component/controls
- I would like to see Developer Express like component/ Form controls in ms access and the ability to compile the runtime to a single, and independent EXE without conflict to any versions installed in a client machine.. This idea i think will decline the sales of VS and no one will jump to codegear delphi.
- —Guest Erwin Leyes
Support for Multiple ERs
- I would like to see the ability to create with an easy interface, Multiple Entity Relation Ships like SQL Server
- —Guest Julian
Previous31-43 of 43
