The Next Version Of Microsoft Access - Have Your Say 

by Garry Robinson, Microsoft Access Author and Developer

This page has been setup to provide a central location for people to post and review  ideas for the next version of Microsoft Access plus one (guess is now 2009). This is a follow up to the previous initiative for Access 2007 that ran to 220 requests from users.

As Access 2007 is now being distributed around the world, Clint Covington, Senior Program Manager, Microsoft, wants feedback from people about the next version of Access.

Click here to add your own ideas to Clint's Access 14 (2008+) blog page anonymously

Note: You may want to review what is new in Access 2007 here

Thanks for reading this page and don't forget my popular newsletter to keep up to date with all the latest Access and programming gossip.  Garry Robinson

-----
The complete list of ideas posted in 2005/2006 by users follow. Feel free to use for inspiration for Clint's list.

General Issues

1 More user-friendly database templates. e.g. the music collection template requires so much re-design for a book, coin, stamp, etc collection you have to start from scratch. Access is not intuitive in any way for beginners.

2 Redesign the GUI in the Northwind database to show off some of the more interesting form and report features, instead of the usual generic boring column oriented look. e.g have some unusual graphs, tabbed forms, creative use of color, ActiveX, etc. Some of us are good with data, but have zero creative ability in form and report design. A good example is a great start.

3  Ability to have multiple versions of Access work and play well together on one machine.

4  Better Database and VB Project stability. All too often we spend a fair amount of time recovering from (if possible) database corruption issues that are not always well documented in Microsoft's Knowledge Base

5   Supported decompile. So many problems in Access databases lead back to compilation problems in a specific object (usually a form, module, or report), that it's ridiculous that the only solution to the problems is an "unsupported, undocumented (well, barely documented since it can be found in the MSKB, but it isn't easy to find)" command-line option. What would be nice is a way of identifying which object is causing a crash and the ability to force a decompile of the database (and complete removal of all compiled code) from within Access.

6 Decompile as a menu item and with full MS support.

7 Support for the Mac

8 Easier to use for beginners like File Maker Pro

9 promote Access more so people don't buy and use FileMaker when they already have Access installed.

10  Include Access with Office standard or the Office Small Business edition. Even if this were only a "lite" (read: "crippled") version of Access that was easy to use, it could increase the groundswell of Access users quite considerably. Eventually this would translate into a lot more Access work for developers as the lite databases that actually prove valuable have to be converted into multi-user business databases.

11 There should be a database-specific option that prevents people from using reserved words, words with spaces, and special characters (such as percent signs) to name database objects such as tables and fields. This should be turned on by default in new databases. This would make both Access development and upgrading to SQL Server much easier. I also really doubt that inexperienced developers would object to these restrictions. While Microsoft is at it, this option should also be responsible for stopping the control wizards from producing meaningless names for controls like Command17. The wizards should either generate meaningful names (like cmdExit) or give the user a chance to enter a meaningful name.

12 Larger max database size, larger internal constraints such as number of fields in a query (256), number of relationships for a single table (32).  The PC has moved on !!!

13 Provision of a public key/private key arrangement within the workgroup file so that it will be possible to time-out or re-activate an application when a licence expires.
14 Why is usage of Citrix and Terminal Server not promoted more. This is the answer most of my customers have chosen to solve DLL-hell, virus-protection, cost of ownership and cost of implementation. This new technology together with Virtual-PC gives so many new possibilities in system development that they must be accounted for in the future development of Office. Don’t be blinded there are other protocols than HTTP, RCP for example. Instead of moving data it is possible to move keystrokes and mouse movements…

15 The ability to easier read data in the most common ERP-systems today (SAP, Movex… ). I know most of them are closed, very closed. In the past this has not been a problem for Microsoft, I remember read and update Paradox and Dbase-files in the first version of Access better than in the original product.

16 All multiple versions of Access to co-exist without conflict. Users don't need to do this but it is extremely important to developers. Changes made to A2K2 and A2k3 are a step in the right direction but saving in an old format is not quite enough. I need to know that I am not using something not supported by the previous version.

17 There needs to be a separation of "general Access development environment" settings and settings for a particular db instance. Custom menus, for example, need to be separated into what the customer will "see" and what the developer will "see". Perhaps a db open setting that identifies "customer" or "developer" mode could be used to implement this.

Database Container (Modified into a Task bar in Access 2007)

18 And, perhaps some way to group subforms with the form they live with; queries with forms they run; or at least document/label these.

19 Allow you to select multiple items from the database container using shift or control and allow you to delete/open, all at once.

20 Menu for printing tables in design view (the documenter is too cumbersome), with the ability to select one or more tables for printing.

21 Full Search & Replace in Zoom window for expressions.

22 Allow opening a subform when the main form is open (if necessary, close the main form – but do it automatically).

23  The Groups feature is great, but I occasionally have to import all my objects into a new database and I lose all my groups. I'd like to see these as import items as well.

24  Useable and useful groups (I haven't used A2K3 yet, so maybe this has been improved already but for A2K and A2K2...). A few things that would improve their usability: Ability to use them to import and export objects. Ability to import/export group definitions. Non-static object information (including the ability to rename and delete objects from within groups). Ability to use limit the objects you see in other places in the system based on groups (e.g. Add Table/Query to a Query dialog box).

25 When importing objects from another file, there should be an option to replace, rather than import and tack on a "1" at the end if there is another object of the same name. I frequently use numbers at the end of my tables and queries for my own tracking and when I need to import it's very confusing which object is my original and which is the import. It would be better if the program would tack on the word "copy" at the end when it encounters another object of the same name. This suggestion also applies to situations where users drag objects from one window to another (where each window is a separate database).

26 When naming objects, Access doesn't allow periods -- keep that rule but have the error message actually state it's because of the use of a period, not just 'Invalid Name'.  Would be very useful to new users making that mistake.

27 I would love to see Access (and SQL for that matter) follow a standard 3 character prefix for naming of objects, fields and others. This way when you receive a file from somebody else, you know by the name what type of thing your dealing with. For example if you see a field on a form and it's name is intOther you at least know it's an integer.

Tables

28 Ability to copy data out of the table design window for quick documentation.

29 Also, easier access to the built in documentation of tables and fields in access.

30 Why can't I copy data out of the table design window? This looks and behaves like a datasheet but if you click in the upper left corner of the design window to select all of the rows and columns you still can't copy that text. Why not!!?

31 Since Access 95, all I've ever wanted was for Access to be image friendly and be able to grow large enough to handle them.

32 Similar ability to do Find and Replace within the Table/Query/Form/Report Design windows.

33 Make the Linked Table manager more useful (Allow you to size the window so you can see long paths, allow you to group the links by back-end, so you don't have to hunt for the oddball back-ends, etc). These 2 alone would be relatively simple to code and would be GREATLY appreciated, I'm sure.

34 The linked table manager is a joke. This needs to be redesigned to work better with databases that use multiple back-ends. There should be the ability to select by a common backend so you don't have to scroll down the list and pick out the ones you want. Alternatively, there should be a sort option by source. Also, the window needs to be sizable. Too often, the pathnames are too long and it's impossible to read which tables come from what backend file. If I didn't have a written list, I'd never be able to use this feature (and often don't simply because it's too cumbersome).

35 Larger text fields (> 254 char), or more options for memo fields, e.g. sorting, viewing the entire memo, not truncated, on reports. Format-able memo field info, e.g. my memo might have ten lines, one of which I would like to store as bold, underlined text, maybe in a different font or size.

36 Triggers or some other such event tree on Jet tables and Access queries that fire for data manipulation. Most of this currently can be kludged in forms, but this is the wrong place to do a lot of this kind of stuff.

37 Maybe replace Jet internally with Cloudscape (http://www-306.ibm.com/software/data/cloudscape/), or just make Jet a compatability layer on top of MSDE.

38 A resize all columns command (that uses the entire recordset)

39 No automatic default value for table fields! (Whoever thought that every number field should have a default value of zero was a good idea, and didn’t provide a way to turn that “feature” off, should be taken out back and…)

40 An improvement to the autonumber system so that on compact all the holes are filled in would be wonderful. Obviously, this would require cascading updates in all tables linked to each other through the autonumber field.

41 Encrypted field support

42 Sixty four bit integer support

4 The ability to generate Database Setup and Update Utilities or scripts. This would greatly ease deployment (especially for updates).

45 Support for Identity Set Primary keys (where the key is (server or site id, autonumber incrementing unique to each site id rather than autonomously).

46 The ability to insert into Identity (Autonumber) columns or let a value be generated.

47 Support Replication using Identity sets and collision handling rules.

48 Better way to document tables, queries, modules, etc...something similar to what FMSInc offers.

49 Ability to export the DDL for a table or set of tables to facilitate rebuilding tables.

Queries SQL/Query Editor

50 In the QBE, there needs to be a way to drill down to another query used as a data source for the existing query. It's a real pain to have to close the current one, open the other query and make changes, then come back and finish the first one.

51 Easy way to handle conversion of Nulls to zeroes or zero-length strings. This could be the default in some instances.

52 Support for theta-joins joins using (<>, >, >=, <, <=) arguments and Union queries in the query design window.

53 Currently, when you switch back and forth between SQL view and Query Design view, any formatting (line breaks, etc.) you put into the SQL view disappear. If formatting in SQL view could remain, it would be much easier to use the SQL view.

54 On the SQL editor, wouldn't it be great just to be able to do a find and replace and a few other normal text editor features.

55 Ability to do Find and Replace in the SQL View window. In fact this window could do with sprucing up - add basic formatting and colour-coding features like the IDE.

56 Wouldn't it be great if you could convert a SQL string to VBA code, without having to go look for a 3rd-party utility?

57 Click on a source query or table in the top pane of the Query Designer to open it in another window.

58 When opening a query or SQL statement from a RecordSource property, the window should not be modal.

59 The ability to create certain types of queries from within the query editor, such as union queries.

60 A SQL view window with usable capabilities, such as find and replace, help file integration, etc.

61 In crosstab queries, why can't the program insert zeros in the fields where no data exists?

62 When creating update queries, in the update to field when I type in a field name without the object name, it gets converted to a text string in quotes. If I don't catch it and take out the quotes and put in square brackets, I end up updating all rows to the text string, rather than the value I wanted. Please, can't this be fixed to assume users want the field name?!?

63 Stored Procedures and Triggers in Jet

64 Compacting through SQL.

65 The ability to do anything DB modification or query related through SQL that you can do with the UI, and actually have the statements documented.

66 Ability to add REM statements to SQL statements when viewed through QBE.

67 Could anyone tell me why there is three tools for developing an SQL-statement delivered with Office: MS Query in Excel, QBE in mdb and the stuff looking almost like SQL Enterprise Manager in adp. And most strange of it all, the best tool of them all, QBE in mdb, seems to be stopped when it comes to new functions.

68 Update queries should be smarter. They should allow updating whenever specific records can be identified. Queries that use Max(), for example, to find a record in one table in order to use the key to find a record in the table they want to update won't work. It would be fine to place the onus on the developer when implementing this and restrict the updating to the outer query.

69 We need something similar to the SQL Query Analyzer. Mainly the Rollback feature, so that we can test Action Queries, but rollback the changes if it wasn't correct.

Macro

70 AutoKeys Macro:  Give us a solution without a macro.  AutoKeys is the only macro we (must) have and I want to get rid of it.

71  I would like to see the long neglected Macro language be made more useful.

Forms Design

72 Generally, the inexperienced user likes big buttons that say Save or Find or Add Record. I believe that the form wizard should include these as a default option. In my humble opinion, Microsoft needs to take Access back to the usability labs and rework the form wizards and related items to produce forms that make sense to mere mortals.

73 My first request is to improve the basic forms interface. In my humble opinion, Access in its basic state needs to become a whole lot easier for the naïve user to interact with. For example, if you were to create a standard form that worked with a table, and then give it to someone who has never used Access before, that person wouldn’t have a clue what to do. The default form generated by the form wizard comes with navigation buttons way down at the bottom of the form, a well-hidden record selector, and some complex toolbars and menus that are designed for both developers and users and don’t really work well for either. I’ve yet to come across a typical user who looks at the menu bars and toolbars to figure out what to do next (and even if users did that, they probably wouldn’t pick anything that would actually help them). 

74 Would like to see a container control such as the vb6 frame control to ease making groups of controls visible or not visible.

75  I too vote for grouping of objects in a form or report. How about being able to name an object group and then being able to collectively set colors, enabled/disabled, and visible/invisible status.

76 How about global search and replace across all controls of a specific type, such as text controls.

77  Would like to see a grid control with the capability of True DBGrid Pro, or a version of Access compatible with grid controls like True DBGrid Pro.

78  Extend the functionality of continuous forms. Be able to manipulate the same controls in different rows independently of each other. Now when you try to manipulate a control on the continuous form like disabling, for instance, it applies to all instances of the control (all the rows of the form). Also a setting to highlight a specified row by changing its backcolor independently of the rest of the rows (goes along with my first point).

79  One of the main annoyances I have was the same in both Access 2000 and 2002 (XP). In the Form and Report Design Mode, When I copy and paste an element between forms/reports, the pasted elements come in at the top of the section of the form I'm in. Why can't the element be placed where my cursor is when I right-click and select paste.

80  Allow you to paste an object onto a form where you click, rather than at the top of the section.

81   I would be delighted to be able to use italics in a memo field in a table (for latin names).

82  I would like an easier way to apply formatting changes to objects in reports and forms by being able to treat them as one object or collection.

83  A standard button for adding a group of BIG navigations Buttons to our Forms. First/Previous/Last/New for example

84  Allow you to copy both a button and its code from one form to another. Make it an option.

85  Click in sequence to set tab order of form controls.

86  I want to be able to zoom in during form design. We actually purchased Crystal Reports not for any of the advanced querying or what have you, but because some of the very complex forms with lots of boxes and such were simply too difficult to create and manage within Access. Multiple zoom levels, PLEASE.

87 Continuous forms *could* be useful, but they are so hamstrung...

88 Oh, and while we're at it, add some true OO to the hierarchy. You know, like inheritance. It would be nice to make a form that has some generic functionality, and make new forms inheriting from that form...

89  Usable form templates

90 A built-in RTF memo field. Yes, it can be done using 3rd party controls, but that shouldn't be necessary.

91 A wizard to create a form that has input (new record) on top of the datasheet or continious form.

92 Allow Access to iterate through a form/report controls collection in the order they appear on screen not in the order they were created.

Better Controls

93 Automatically name objects and controls according to LNC (you suggest something close to this) 3. Zoom for form and report design 4. "Pin" controls or groups of controls so they can't be moved or resized inadvertently.

94 A more robust image control as a native control. (I.e., one that supports scroll bars or panning. One that supports right-click for changing the size, copying, etc).

95 The Insert ActiveX Control list should only list controls that work on Access forms. It should be possible to open Help for each of these controls from the Insert dialog, and from the control itself. All events of the controls should work in Access, and (where relevant, such as the TreeView control) they should be bound to data.

96 Include a set of well-documented ActiveX controls (with all supporting files) that work on Access forms, which can be distributed with Access applications. Note: Documentation for these controls should be Access-specific, i.e. it should explain how the controls work on Access forms.

97  Sell the ActiveX control sets separately, similar to Font Packs, so people who want to use them can purchase them without having to have the Developer edition.

98 Colors on command buttons and tabs would be a good improvement. Being able to format text in a text box with different parts of it being bold, italic etc. using some system like html tags would be a great improvement.

99 Being able to group controls and to freeze them in their locations would be quite helpful.

100 Coloured command buttons.

101 Include "web-style" buttons, menus, etc. That way, you can develop in Access, condition your users to what an Internet appearance will look like, and then switch your app. to the Net.

Reports

101 The ability to fine-tune report layouts in a preview window by dragging/bumping fields and labels with data. The one feature I like that Crystal has over Access.

102 A simple or simply programmed way of sending reports as emails extracting address etc details from a query would be very useful.

103 Also, Why is there still a 22" length limit on report & form sections. In a report this is only about 2 pages. I had to go to a tabbed interface for my 53-question survey results instead of presenting them as one continuous form. Same problem with reports. I have a 53-question survey, some with multiple parts and some of those parts are multiple choice. For example, I have one question that has 10 different sub-questions, and each sub-question can have 3 possible answers. That's 30 line-items for a single question. It's a pain in backside to have to do this through a series of sub-reports.

104 Margins visible on reports, and controls can't be moved or resized outside of margins.

105 Reports should have header/footer handling comparable to Word (allowing separate headers/footers for the first page, and separate left and right headers/footers).

106 Reports should support many more paper types and sizes, similar to Outlook.

107 Regardless of how report groups are set up, and new pages forced, Access reports should never print blank pages.

108 Allow selection of different printer trays for different report sections, say Tray 1 for the first page of a report, Tray 2 for the remaining pages; or Tray 1 for a letter, Envelope Tray for its envelope.

109 I want to be able to double-click a sub-form or report and have it open in a new window, change it, save it and continue with the main form or report. It used to work this way. Now my tiny .25" tall 'can grow' sub-report can't be edited without closing the main and opening the sub, then closing the sub and reopening the main to see if my change was satisfactory.

110 A printout command that tries to fit all the columns on the page

111 A useful report wizard

112 Vertical alignment properties on labels (really important for lining up column labels when some are multi-line and others aren't). Plus it's helpful when you're changing label text at runtime and don't know if the text will take up one or more lines. It's available in Word tables, Excel and PowerPoint -- why not Access?

113 I can't tell you how many times I've created a new report that prints fine on my printer, but when one of my clients tries out the report, one or more lines will be truncated (I assume due to a font incompatibility). Isn't there a better way to manage fonts substitutions so this doesn't happen, or a way to package the fonts with the database?

114  Why can't we have a true Send to Word 'doc' file which maintains graphics --- the old and only way of RTF is way outdated.

115 Ability to generate and/or save more types of reports i.e., create PDF reports, etc.

116 Remove the issues with the default printers

117 Option to display the report footer at the bottom of the last page rather than following the last detail line.

118 Support the concept of Sections for reports similar to Word documents so part of a report can be created as portrait and part as landscape.

Programming VBA

119  Add an event to prevent someone from closing the application by closing the Access window. There are OnClose events for forms, but it's pretty limiting if there's no OnClose event for the whole application. Seems like that would be a more important event to trap.

120   Built-In Objects for returning PC Name, Logged User Name, Domain Name, IP Address, Etc. Perhaps some of this is in 2003 but I haven't had any experiece with it and have had to use API calls to get at this information.

121 References to other Office object libraries should automatically upgrade or downgrade to the Office version in use when a database is opened. (Word and Outlook references in particular don't downgrade.)

122 Macro recorder, that saves macros as VBA code (for automation of end-user actions).

123  Packager can handle standard Office tasks automatically, such as putting Word or Excel templates in the correct folder, creating Outlook folders, publishing custom Outlook forms, etc.

124  Built-in boilerplate code storage for easy access when working in VBA code.

125   More information about API calls. Everything I have learned about these came from user-groups or sites they pointed at. I think a section in Access Help should contain info about these. Where does everyone learn this stuff from?

126  A transfer text command that allows you to specify the qualifier and delimiter

127  Access could do with a database wide activity event so that the database could be shut down if there is no activity by a user after a set period of time. Also a database method to contact people using a database would also help with management. Shutting down a database is important for upgrades, compacting and backups.

129  After requerying (from code), the form should still be on the same record as before the requery (instead of going to the first record).

130 Better transaction handling.

131 An application on-start and on-finish event would be good.

132 Wizards should stop generating DoMenuItem code that refers to Access 95 menu items. Even worse is the fact that the generated code uses numbers rather than constants so unless you have A95 installed, there is no way to figure out what the generated code actually does. Most users don't understand that they should give their controls proper names so I get to look at code for Command117 that runs item 5 on some menu from a 9 year old version of Access and figure out what it is intended to do.

Error handling:

133 Centralized error function

134 A function defined at database level (property for example) that should get control in case of an error not handled at individual functions or subs. Currently I am using error handling in every function and sub, but almost 80% of the error handlers are the same - it's just to much of redundant code.

135 The Err object should have new properties to get the following information:
- Name of the function or sub where the error occurred.
- Invocation stack (we can see it now but not get to it by code).
A nicer method than the ugly Erl to get the line of the error would also be nice. Code with line numbers is not very easy readable.

136 Built-In, better global error handling would be nice. Then you could have One all-encompassing routine with say a case statement to deal with errors returned by different procedures, etc.

137 Optional standard error handler in procedures.

138 An option that, when set to Yes, makes it possible to go to the code (or control, or whatever) that caused an error, for all error types (no more mystery "Invalid use of Null" error messages or parameter popups). This option would be set to Yes for developer use, and No for end-user use.

139 A way to totally suppress Write Conflict messages with a default action.

140 Just want to second the comments made about error handling and security made earlier

145 More understandable error messages

VBA IDE Enhancements:

146 Please, please, please provide a list of table and query names in the VBA window so when writing code I can look it up (and even better - copy), and I don't have to keep switching back and forth or writing the names down on scratchpaper.

147 Bring back the Expression Builder for use in code.

 148 Support the mouse wheel  on Microsoft mouse work in module window. Ability to scroll in the Access VB IDE. (Note: there is a solution to this -- look at MS KB article 837910 and the starposts on wopr.com for how to implement it, but this really should be built into the IDE.)

149 A search option for Code only or Comments only.

150 Ability to decompile

151 Spell check my text in quotes

152 A command to close all my open modules

153 In VBA, to be able to get the call stack. It's visible on the menu, so why don't I have programmatic access to it?

154 The VBA subs are supposed to sort alphabetically, but they get out of order. Would like a way to resort the subs into alpha order.

155  When picking an object in the VBA window, a sub in created automatically before I can pick the procedure I want. Then I have to delete the insert and pick the procedure I want. Can't it just wait until I pick both?

156  When entering If or SelectCase statements in VBE, why can't the editor automatically insert the End If or End Select (similar to the automatic End Sub and End Function). This would save considerable time and frustration.

157  Every new sub and function should be created with automatic error-handling, similar to what's provided with the command button wizard.

158 Automate more functions. Why do I need to spend so much time dinking around with little bits of code?

Security

159 The bypass key (Shift) needs to be changed as it is to well known.

160 The database and VBA passwords need to be encrypted into a better place in the file

161 Shortcuts shouldn’t reveal the location of the database or the workgroup file.

162  If security is to remain in its current rickety state, developers need new functions that take advantage of Windows 2000 user and group names and .NET encryption functions. These need to be callable without reference to complex Windows functions. These should work like the intrinsic Office File Dialog and the File Search VBA functions that were introduced into Access/Office 2002. These should take into account the domain login account, not the local login account.

163 Security aware functions in VBA

164 At present you have to do rely totally on the Windows API when it comes to security. This is quite a nightmare. Perhaps .NET could solve this.

165 Never, ever get a message about not being able to save something because another user has the database open when you are the sole user of the database.

166 Would like to see field level encryption using a variety of available technologies without paying a fortune to license third party technologies.

OLAP

167 Add more OLAP -- I would like to be able to create/export a data cube directly from an Access database. I am using Access to hold valuable data and the ability to create the cube directly in Access instead of using Excel would be a productivity boost. It will also make OLAP more accessable to all Access users.

XML

168 Right now, moving data in and out of tables in Access using the XML facilities is far too hard to do--you really have to know XSLT if you want to convert data between its original format and the format that Access requires for the data to be correctly imported into a table. It would be great to have a set of tools (maybe like the BizTalk mapping tools) that would support generating XSLT to handle the conversion. It would really open up Access' XML facilities to the masses. 

.NET

169 Let us be part of the future and let us use our current code (with reasonable effort).

170 It would be great if Microsoft could design a conversion utility that could convert Access databases into .NET applications.

171 I would really like to see a merging of Access and VB.Net. Access would gain the power of VB and VB needs the user-friendly development tools of the Access forms, queries, and reports. For instance, VB has no subform control, which I use all the time in Access. True, it has a grid control, but my Access subforms are often not grids.  Ed “Sounds like a request for .Net as much as a request for Access.

Switchboard, Menus and Toolbars   (Ribbons in Access 2007 change these items)

172 Custom menus are great, but more options are needed. That is, there should be a better way to open and work with the menus (some menu lines can get long and when opening the properties it gets hidden behind the menu and there's no way to get to the form to view the data). Also, if I make a mistake in editing/adding/deleting, there should be an undo option.

173 Make menus work like VB6 which each item is allocated a name that then has a click event.

174 It would be really good if the Switchboard could be tied in with Windows User names. It would also be very useful if the Switchboard offered more options such as open forms in datasheet mode or readonly mode.

175 Make the creation of shortcut menus easier.

176 Much better menu item icon editor tool.

Office Compatibility

177 The Exchange/Outlook Wizard should set up two-way links between Access tables and Outlook folders, including all standard and custom Outlook fields, with tools to set up relationships between linked Access tables and flat-file MAPI databases.

178 Excel: If I set up an Access report that looks like a well designed Excel worksheet, I should be able to export to Excel and have it look exactly the same.

179 PowerPoint: If I create a graph using Access data, which I would like to show in a PowerPoint presentation, there should be an easy way to export the graph, either as a graphic (e.g. emf, bmp, tif), or as a PowerPoint slide or presentation identical to the Access report. Some of my reports have up to four graphs on them, and lines and boxes, and snapshot format totally destroys most of it. However, users want this report on a page of their presentation.

180 A sendobject command that allows the object to go into the message body instead of an attachment 9. Allow multiple attachment on e-mail

181 Inclusion of more MS Excel functions in VBA would be useful. Addition of more statistical functions (such as those for median, mode etc.) would also be welcome.

182 I’d also love to see Excel become the second report writer for Access. I use Excel through a combination of automation and templates all the time for my Excel-mad customers, and I sure would like to see a lot more integration in this area.

183 The ability to write queries to access Outlook PST files (or even better across multiple files to get around the search limitation currently in Outlook). Alternately PSTs could be added as a supported Jet type.

184 Fix importing data from Excel. In text data files you can define the column's data type. Currently Access decides this for you then fails when it's wrong. This is classic for social security numbers which Access views as numbers and drops the zeros on the left. Also for zip codes which Access also decides are numbers and then fails to import when it encounters a long zip code with a hyphen. You'd think they would have figure this out by now. At minimum allow the user to define the data types of columns.

185 Better compatibility with other Office products.

186 Exporting a report to Word or Excel should maintain formatting. Both products support graphic elements so Access should not strip them.

Jet Engine - Performance

187 Improve the Jet engine and "Linked Tables" to behave more like a true "Client/Server" architecture. Most developers split the database in to a front-end/back-end approach anyway. It would be nice if the server did some of the processing work instead of sending an entire table-set for the client to deal with. I know this may be stepping on the toes of SQL Server and may be bad marketing but from my selfish stand-point it would a good thing.

188 Some way to view bottlenecks - I have some forms that open very slowly - some way to analyze the form and say what it was doing and how long it was doing it when it opened, or ran a function.

189 EMail replication option for remote occasional users as well as current indirect/direct/internet methods.

Links >>>  Home | Search | Workbench | Orders | Newsletter | Access Security | Access professionals