Thursday, September 30, 2004

Access 2008

This blog has been setup so that developers and power users of Microsoft Access can continue to blog your great ideas for the next version of Microsoft Access plus one. To entirely second guess Microsoft, we are anticipating this will occur in 2008. Anyway the important thing is that this is a place where you can have your say early for that version because Microsoft needs about 3 years before release date of Access if they are even going to contemplate an idea. After a year or two, Peter Vogel and I will sweep these ideas together and send your ideas off to people at Microsoft who may actually pay attention to the list. Our last list of requests from users numbered 220 ideas and maybe this time around we can come up with a similar list. The article on this topic will probably appear in Smart Access at the end of 2004.

Remember if you don't bring up your great idea, don't complain if it doesn't turn up.

Garry Robinson
Contributing Editor for Smart Access
Author of Microsoft Access Protection and Security published by Apress.


Anonymous said...

In the Reports section, a report that works with cross tab queries which configures its fields when the report is run. Building the code in the report to deal with this is always a long process and I always get hammered when I filter and one of the columns doesn't appear.

Anonymous said...

1. Simple mechanism to determine screen resolution and change form objects size to match.
2. More use of colour in the design process so that eg related queries could be easily identified.
3. automatic tooltip display of date when object last altered (on/off switchable)
4. A mechanism for finding the library that has gone missing / changed when updating from one version to another. Code which is broken by an upgrade should not be, and when it is the steps to repair should be shown.
5. Clarification of which bits of code are VB for Access and which are VB in its various flavours.
6. If documents broke every time word was upgraded it would have long since been withdrawn, why is Access not subject to the same discipline. Since some routines in a db are used infrequently some breaks may not appear for months if not years by which time the developer has......

JaxMama said...

I have never understood why Microsoft could not give us the ability to align form and report controls by CENTER or MIDDLE, instead of just top, bottom, left and right. All of their other products provide this option, and I absolutely can't stand that I can do it in Access!

Anonymous said...

Allow the "Default value" property of a table column to be generated with any function not just built-in functions.

Anonymous said...

Help menu: Bring back the index lookup - on line only doesn't work and is a nightmare! Add more items to the VBA section of the help menu - perhaps a separate help menu dedicated to VB methods.

Find and Replace functions: Allow Access to search and replace underlying VBA code sets for forms and reports. Currently you can do this in Queries, but it will not look at underlying VB code tied to forms and reports. Would like to see the ability to view all VBA code included in the entire database, much like VB6 allows you to view all code for a project...

Anonymous said...

Restore the ability to import Monarch generated .prn files to Access. Access 97 allowed this file type, but Access 2003 does not. You have to generate a txt file from the prn, thus adding another step to the process. Give us back the .prn import ability!

Charlotte said...

Integrate the VS.Net IDE and allow use of .Net code and user controls. Make the forms design more like VS.Net including the data binding and the use of panels or groupbox controls to group controls on forms. I'd like to see that as an option so that VBA programmers could continue to use their existing code while .Net programmers would feel at home in Access. The .Net IDE is superior to the VBA IDE once you get used to it.

Recognize Access as a development platform (yeah, right!) and provide the tools that developers can use effectively, not just those for power users and wannabes.

Garry Robinson said...

Terry Dillion from Victoria sent this one in by email

I would kill for

Control Arrays on forms as in VB.(Wishes number 1 2 AND 3)
Better more accessible column sizing & positioning in datasheets (Datasheets are the most bestest thing since sliced bread).
Make more accessable alternate row colouring
Picture property for buttons which allows you to design decent buttons
CanGrow property for subreports based on Word documents
Would also like
Built-in documentation
Decent relationships builder with ability to zoom and save a picture of the page for documentation
When copying objects between forms have an option to also copy the code
Formatted text in memo fields
A decentTreeview control

Teedee Computing Services

Anonymous said...

Fix the locking so that forms/reports can be edited (like access 97) while the database is open.

Eliminate the problem where publisher 2000 or 2003 hold exclusive locks on a database! The idiot who thought a report writer should use exclusive locks should be fired.

Fix the import data feature so that it doesn't lock out fields from changing the data type from number to text.

Fix the interoperability problems when working on access 2000 database from 2003. 2003 crashes the database without any useful information provided.

Fix the problem with large reports with many graphics. (access 2000) Once I get over 400 pages, access blows up with an out-of-memory error, or generates output that causes a postscript printer to blow up with an Image error. Initially I thought this was the device or driver's fault, but it happens across 3 different printers and a PDF writer. It also happens on multiple versions of windows (2000 pro and 2003 server) Everything is fine if you limit the number of pages that you try to print.

Scott Lee
Superior Labels

Anonymous said...

Allow to lock objects/controls on forms like VB.NET
Closer to VB.NET, new syntax and functionalty VBA.NET.
Only WORKING ActiveX controls in ToolBar.
Self recovery method to find and register libraries.

Anonymous said...

I think MsAccess must be independent from MsOffice in future.

Garry Robinson said...

After working with a database administrator with a commercial background who had to write the occasional update query, I believe the update query designer should be redesigned so that the fields where the data is coming from is on one panel and the fields where the data is going to is on another. Then the user could draw lines from one field to another to help build the queries. Also the environment should somehow show you before and after before the results are committed. THere is no way of knowing what is going to happen till it is finished.

Anonymous said...

We shouldn't have to compact access. It should automatically, manage this function itself.

I'd also like to see "Views" as in SQL Server

Security is a joke in Access. You can change someones permissions and it doesn't work (or doesn't work immediately). Definitely some funny stuff going on here. The number of times I've had to create a new user with exactly the same permissions as the one that doesn't just to get it to work is ridiculous. Let's have it a bit more like SQL Server.

Grouping of objects would be useful. When you have tens or hundreds of forms / tables and queries it gets hard to navigate.

Much more easy integration with Word and Excel in particular. The theory of how it currently works is sound and it's all very modular. But in practice it's a lot of code. Does anyone remember the package "Smart" which integrated a Database / spreadsheet / wordprocessor and communications package all in one with an underlying programming language. Fantastic and ahead of it's time. Microsoft could learn from this.

Adrian Murphy
Director - 360 Software Ltd

Anonymous said...

Allow more than 8 items on a Switchboard

Anonymous said...

I would like to see the following;

1. The ability to display an attached menu/toolbar inside a pop-up form.

2. Ability to choose the colour of the tabs in tab control

3. The ability to place the tabs of a tab control at the top/bottom/left or right of the control

4. Ability to change the colour of pushbuttons, their shapes and also the ability to include both an image and text.

5. More glyphs

6. A mouse over event for all controls eg. buttons, text boxes etc.

7. Smart tags that don't require you to have degree in computer engineering to create.

8 More than 32 indexes/joins per table.

Thanks you...

Anonymous said...

1) One improvement to the HELP(~less) system would be to include some CONCRETE EXAMPLES of EVENT SEQUENCES especially for common coding/UI scenarios.
For Example, what are all the events that fire - and in what order - when a user clicks on a control in a subform from another control in A) the main form and B) another subform? This should be shown in the HELP.

Better yet - Build-In an optional tool to SHOW the developer what events are occuring in a given UI interaction scenario - whether or not the events currently have VBA code modules attached! The tool could let the developer choose what level of detail (or even specific control) they care to see.

2) In the VBA IDE, how about a quick and convenient little tool to get a "distant control"'s RELATIVE name?
If I'm working in form A Design view and want to reference a control in form B (whether it's open and available in the IDE or Access Window in either design, normal, or heck, even spreadsheet views, or not open yet); a right-click Pop-Up Menu item to "Get A Control Name..." should nab me a new type of cursor pointer that stays until I either hit escape or, possibly after several other clicks to get to open/select the right form (to allow clicking in other windows and possibly scrolling to the control I need), right-click and choose "Get This Control Name". Then the correct relative control name is pasted into the previous window (which jumps back up in focus automatically) exactly where I was when I started the "Get A Control Name..." operation.
This feature should operate also in the Query designer and Expression Builder.

3) I've seen errors occur in forms and reports that provide NO CLUE to diagnose the damn things. If there is no operative Error handler running in VBA Code, the Built-in Access error handler MUST pop up a window that tells the user REAL, USEFUL Error Information. Something like "Record 1, field [fieldnam] caused an 'Invalid Use of Null' Error in Control 'Text23' in Form 'MyForm' During the Form_Current event." (even if there is not a VBA OnCurrent Event handler for that form!) - not the currently COMPLETELY USELESS "Invalid Use of Null" error that can pop up now!

Vansworth said...

I always wanted a way to hide the MDI parent (the MS Access frame) independently from the MDI child the Access application form in access, but could never work out a way of doing this in VBA. The Parent - Child thing can be a bit clunky.

I can create cool applications, but I feel frustrated by the limitations on the ability to create an interface

Garry Robinson said...

I use Access as a design tool to manipulate and manage large groups of data and as such my databases are extremely dynamic and may contain a large amount of tables, queries or reports. Some of these are use quite often while others are used are only there in case I need them again and don’t want to build them from scratch. The change I would appreciate the most would be the ability to group these object into different directories so I can efficiently organize my database and not have to scan through endless lists of objects. I am not very fond of the shortcut system which simply provides a different spot to find particular objects but little in the way of organizing.

Ross O'Flaherty (via Garry)

Anonymous said...

Regarding this "security" feature comment:
159 The bypass key (Shift) needs to be changed as it is to well known.

And who will be the only person in the whole wide world who will know what the new key is? You? No? Then noone? Okay. If noone knows, or if only Microsoft knows, then why have the key in the 1st place? Will we have to call Microsoft to have THEM remote in and use that special key on our database every time we want to bypass the startups? IE: Hide the special key equals Do away with the key. Who came up with that one?'s "too well known" not "to well known".

Anonymous said...

In a Macro, why not have a function IfExists. For example, if I have a macro statement to delete a table, I only need to delete the table if it exists. I haven't found a Condition statement or a Microsoft built-in "IfExists" function.

Anonymous said...

Apologies if any of these were previously referred to....

1. Native Rich Text/HTML formatted fields for forms and reports so you can have multiple, separate texts formats in the same field.

2. Fractional font size support for the abovementioned fields.

Anonymous said...

The ability to select non-consecutive items in a subform.

Anonymous said...

It would be great if access could adecuate de content of an aplication and resize it in order to optimize it for the screen resolution of the user.

Anonymous said...

Either be able to freeze columns in continuous forms, or be able to have totals at the bottom of the datasheet.

Anonymous said...

I would like to See a TreeView Wizard that was included in Earlier Versions of Access. TreeView Controls are Common in the Software Industry, and Creating them in Access is not Easy by Any Means.

Anonymous said...

I would Like to See Better Web Enabled Applications in Access. A Web Application Wizard would be an Excellent Addition. Even if it was an Application that Could be Purchased Seperately. Point - Click - And Access Apps are on the Web!

Anonymous said...

More Add-Ons.
Microsoft should sell more add-ons for Access - Maybe things like Active-X Controls, Grids, TreeView Controls, GUI Tools, Etc...

Anonymous said...

The query window in SQL mode must have the horrible auto formatting removed and a fixed width font available. I would swap all the query wizards for this.

Anonymous said...

Have VBA examples in the help or another section to help those that do not know how to write VBA code.

qquc1gwar93duhg said...

St0ck For Your Review - FCPG

Current Profile
Faceprint Global Solutions (FCPG)
Current Price $0.15

A U.S. based-company dedicated to the goal of
bringing effective security solutions to the marketplace.

With violent and white-collar terrorism on the rise,
companies are starving for innovative security solutions.

FCPG is set to bring hot new security solutions to
the industry, with currently over 40 governmental and
non-governmental contracts, being negotiated.

Please Review Exactly What this Company Does.

Why consider Faceprint Global Solutions (FCPG)?

Faceprint Global Solutions (FCPG) holds the exclusive
marketing rights from Keyvelop, to sell the world�s
leading encryption technology to be distributed directly
to the Healthcare industry in North America.

Faceprint Global Solutions has completed its biometric
software that recognizes facial features of individuals
entering and leaving through airports, ship yards, banks,
large buildings, etc.

FCPG acquired Montreal-based Apometrix Technologies,
which enhances the companies mission of being a
full-service provider to the multi-application smart
card industry. The North American market appears ready
for significant expansion of price-competitive, proven,
multi-application solutions on smart cards. Apometrix's
forecast of over 300 customers and sales of more than $50
million in North America over the next five years, appears
very realistic, according to company management.

Faceprint Global Solutions is currently in contract negotiations
with over 40 governmental agencies and businesses seeking to use
their encryption, biometric, and smart-card technologies.

Breaking News for Faceprint Global Solutions (FCPG)

Faceprint Global Solutions (FCPG) is pleased to announce that
IBM will now offer the world�s leading encryption software to
its major Healthcare clients in North America.

With FCPG owning the exclusive North American rights to distribute
the worlds leading encryption and transmission software developed by
Keyvelop, FCPG is poised to capture large volumes of sales generated
by customers currently using IBM�s software in the healthcare and other industries.
�This is a very positive move for FCPG and for Keyvelop,� said FCPG
CEO Pierre Cote. �We are very happy about the decision to go with IBM.
This is a continuation of the progress made by everyone associated
with FCPG and its partners.�

Buell Duncan, IBM's general manager of ISV & Developer Relations commented,
�Collaborating with Keyvelop will ensure that we develop open solutions
that are easy to maintain and cost effective for our customers in the
healthcare and life sciences industry.�

Among other things, this new software technology which is currently
being used by a number of European healthcare companies, is used to
send any file, regardless of format or size. Encryption keys, evidence
of transmission integrity with fingerprint calculation, time-stamping
of all actions and status record updating, pre-checking sender and
receiver identities, validating file opening dates are part of Keyvelop features.
About FacePrint Global Solutions, Inc.

FCPG operates a business, which develops and delivers a variety of
technology solutions, including biometric software applications on
smart cards and other support mediums (apometric solutions). FCPG�s
products provide biometric solutions for identity authentication and a
host of smart card- and biometrics-related hardware peripherals and
software applications. Apometrix, FCPG�s wholly-owned subsidiary, combines
on-card or in-chip multi-application management solutions with best-of-breed
�in-card matching� biometrics. Keyvelop�s secure digital envelope solution
and Apometrix�s on-card biometrics work together to produce the winning
combination in the fields of security, traceability and identity management.

The examples above show the Awesome, Earning Potential of little known
Companies That Explode onto Investor�s Radar Screens. This sto,ck will
not be a Secret for long. Then You May Feel the Desire to Act Right Now!
And Please Watch This One Trade!


Information within this email contains "forwardlooking statements" within
the meaning of Section 27Aof the Securities Act of 1933 and Section 21B of
the Securities Exchange Act of 1934. Any statements that express or involve
discussions with respect to predictions, expectations, beliefs,
plans, projections, objectives, goals, assumptions or future events or
performance are not statements of historical fact and may be "forward
looking statements". "Forward |ooking statements" are based on
expectations, estimates and projections at the time the statements are made
that involve a number of risks and uncertainties which could cause actual
results or events to differ materially from those presently anticipated.
We were paid a sum of three thousand USD to disseminate this information from
ir marketing. Forward loking statements in this action may be identified through
the use of words such as "projects", "foresee", "expects", "will", "anticipates",
"estimates", "believes", "understands" or that by statements indicating
certain actions "may", "could", or "might" occur. Risk factors include
general economic and business conditions, the ability to acquire and develop
specific projects, the ability to fund operations and changes in consumer
and business consumption habits and other factors overwhich the company has
little or no control. The publisher of this newsletter does not represent
that the information contained herein are true and correct.

Anonymous said...

I would like to be able to create an exe file. This would be much better than having to install runtime or having to have access on all users computers.

Anonymous said...

The VB IDE in Access 2000 (The latest version I've seen; employer hasn't upgraded) has a Project Explorer window that shows a list of form/report modules and class modules. For each module, I'd like to see a list of procedures and functions. Choosing them from the drop-down lists is awkward.

Also, having to put global conditional compilation constants in the Project Properties window is goofy. It should be in the code.

Access should re-open form and reports where the user left them, not where they were saved in design view.

Access' code generators should encourage a naming convention: "cmdClose" instead of "Command23".

Access should, by default, use system colors and fonts, not hard coded colors and Arial/MS Sans Serif.

Access needs drag and drop abilities like VB.

Access needs a treeview control.

Anonymous said...

I'm am still using Access 2000. If anything I am referring to here was solved in later editions, I offer my apologies for mentioning it here. Ditto if I offer a suggestion that already exists in Access 2000 and prior and I simply did not know of it.

General Issues:

A Database Manager application. You could open it, list various Access databases, and compact, compress, and decompile the databases all from inside this simple application.

Database Container:

A setting in Options that will replace all Design View buttons for queries with SQL View buttons; and changing the default appearance of new queries to blank SQL View instead of the QBE (the main toolbar would still have a Design View button on it beside the SQL View button so that you can switch back and forth if necessary).

Referring to #27 on Do not make MS Access enforce any type of naming schema (especially a non-ISO compliant naming standard). DB objects should not have prefixes attached. If people wish to do this on their own, they can go ahead and do it. But don't make MS Access do it automatically. If the decision goes with doing this anyway, create an Option that has the feature "off" by default.


For Tables, include the following context sensitive pop-up menu options: Generate DDL SQL and Generate INSERT SQL.

A Tables management dialog box where I could select whatever tables I wanted and perform mass Generate DDL SQL or Generate INSERT SQL. The ability to save any particular generation operation as a named object (that can be examined internally to see what it will do). The ability to dictate screen output or file output.

I should be able to open a Table in Design View, open a "DDL" property, and link it to a DDL Query Object. After that, opening the table in Design View will open the DDL Query Object, instead (until the link to the DDL Query Object is undone).

Allow *all* JET SQL DDL to be used directly via MS ACCESS. Including ALTER and CHECK, etc. No being forced to use DAO for basic SQL DDL operations.

A new Object Group: DDL Queries. It's appearance in the Database Window would be solely based on the setting of a global "developer" property being True/False (several other comments call for such an Application-wide global setting). No one but developers needs to see these queries.

JET SQL support for TRIGGERS. Form-based enforcement of this type of operation is entirely unacceptable. this must be contained within the db itself.

Queries SQL/Query Editor

Under no circumstances should any SQL code that I have entered in the SQL property of a Query Object ever be altered by MS Access on its own initiative. () should not be changed to [] (that can create errors in previously functioning queries). () that I did not enter should not appear. Spacing and linebreaks that I enter should remain as they were when I entered them. Etc. There *might* be an on/off Option where MS Access prompts with preview for suggested changes (but given current changes made automatically in MS Access 2000, I would always have it off, never wanting MS Access' changes).

JET SQL support for *Full Outer Join*.

I realize that later versions of access allow the specification of a mono space font in SQL View. This should be considered essential, and should not be removed.

SQL View should allow SQL Server-type comments "--" (all the same rules).

A built-in SQL Scratchpad. Or, better, a Query Analyzer like feature for developing SQL. Developing SQL inside of a Query object's SQL View window is hideously inefficient. The developer would be able to select the text of a query, right-click to produce the pop-up menu, and click on "Create Query Object" (as opposed to copying the text, switching to the DB Window, creating a Query Object, clicking closed the object selection list, and then switching to SQL view, and then pasting in the SQL).

In the QBE, whenever a table name over 8 characters (a changeable limit in Options), MS Access should automatically prompt the user to create a Table Alias (on/off in Options).

Updateable Queries: In an aggregate query, where all the non-aggregating column(s) listed on the SELECT clause are a foreign key, the results are always a list of unique Primary Key values in the foreign key's parent table. Those results *should always be* updateable when JOINed to the parent table of that foreign key as long at the UPDATE operation only alters values in the parent table (obviously, it cannot update back to the child table). I should never see "Must use Updateable Query" when doing the above. The query optimizer should be sufficiently intelligent to spot and allow this. This is also mentioned, in slightly different words, in #68 of

Error handling:

Errors, Global Handling: I approve of the other calls for a global error handling object. Code in each sub or function could then set the values of that object's properties to dictate would happen "on error".

Error Object: I also want a property for the name of the current sub or function. A property for the name of the containing module/class would be even better (not all naming standards are helpful).

Error Messages, Unknown: No more "Unknown Error" messages. If the code terminates due to a problem, that problem must have a valid descriptive entry in the error handling system.

Error Messages, Help For: No more blank pages in the help file after clicking on the help button.

Error Messages, Help File Code Examples: In the help file, there should be *several* examples of code with highlighted portions that can *cause* the error in question. Corrective actions should be listed.

Forms Design:

An objects management dialog box. You would be able to open the manager, and then select a form/subform (or even multiple forms/subforms). Then, you would have lists of all the objects on the selected forms/subforms, by types. You would be able to perform mass property changes on multiple objects.

On a form, I should be able to select a "Set Tab-Stops" operation from the menu. Then, as I left-click on control after control, finally ending with a right-click, the Tab-Stops of those objects would automatically be set in the order I clicked on the controls. This is also mentioned, in slightly different words, in #85 of

Better Controls:

My opinion can be summed up: Make the controls more consistent with VB to increase portability and reduce learning curves.

Anonymous said...

I'm am still using Access 2000. If anything I am referring to here was solved in later editions, I offer my apologies for mentioning it here. Ditto if I offer a suggestion that already exists in Access 2000 and prior and I simply did not know of it.


The undocumented features, ShowPlan and ISAMStats, should be included in the main user interface. No rooting around in the Registry, please! Both could use some improvement. (Hint, Query Analyzer does it right . . . why doesn't MS Access do it right, too?)

DDL Queries open in SQL View should cause a "Drop" button to appear on the Toolbar. Clicking the button will drop that object. (This will save on lots of pointless switching to the Tables group *and* to the Relationship's window to delete these types of objects (assuming that JET finally supports *all* SQL DDL)).

Tables get a group, Relationships get a window. But Indexes? They're stuck inside Design View of each Table. Indexes need to be objects just like Tables and need their own group (a group visible only in "developer" mode). A master management dialog box would be good with sorting and grouping options and the ability to change the name of the index would be good, too. DDL Query Objects creating Index Objects should also be "droppable" via a button on the Toolbar.

A Relationships management dialog box would be good, especially whenever I need to rename many Relationships. Sometimes clicking those thin lines in the Relationship's window and having one-at-a-time access to information relating to them is just a pain in the neck. What if I want to add Cascade options to many Relationships all at once? Sorting, grouping, and filtering by name, parent objects, etc., would all be good.

When in development, any attempt to delete a Table with Relationships on it fails. When this is done, a dialog box should appear in these cases, with the options: "Drop Relationships & Table" and "Cancel" (with "Cancel" having the focus to start out). Maybe have an Option that allows this in place of the normal, "No, you can't do that," message.

Anonymous said...

The example databases in MS Access are a mess. They contain invalid object names (spaces and odd characters), bad examples (see below), and often have terrible db structures. The examples actually encourage terrible usage of MS Access.

The Inventory Control mdb example, during Wizard Creation, on the step, "My Company Information", won't allow the creation of a company with a "postal code" that is non-US. I guess companies in other countries aren't important.

There are many other instances of problems, far too many to list here.

This really does need to be fixed.

Anonymous said...

Better Support for Automation
I would like to automate a specific instance of a secured access database. Currently I can only use GetObject() which does not allow me to specify which instance of the object if multiples are open.

Anonymous said...

For SELECT...INTO, when an output column is wrapped by CBool(), the resulting column should be Yes/No, not Number.

Anonymous said...

DAO 4.0 will need to support all the upgraded elements, features, and capabilities presented in the new MS Access.

Anonymous said...

In a real Relational Database system, the resultset of any SELECT statement must be a relation.

There may be no situations where SQL statements can operate on Base Relations where they cannot operate on Derived Relations.

"Must use updateable query," indicates that JET has imposed an aritifical non-relational barrier into its processing.

This barrier must be removed if JET is ever going to be taken seriously.

Vivienne said...

Hello Garry Robinson, how would you like to buy a beautiful, spacious, character north wales property at a fantastic knock down price. A quick sale is desired hence this north wales property offer website. It's amazing, You can read all the details at this north wales property site. This blog that you have here is great, don’t stop.

North Wales Property said...

Hello Garry Robinson, I would like to invite you to take a look at my beautiful, character north wales property offer. This fantastic north wales property is on offer at £30,000 below the market value because a super quick sale is desired.
This is a great Access 2008 blog that you have here, keep it up.

Anonymous said...

Late binding for form and report ActiveX controls. Much like you can create an unbound subform at design time and specify the form name at runtime. This would prevent the whole application breaking because one control is missing.

Form/report/controls' Width/Height/Top/Left properties in Pixels, not Twips.

Anonymous said...

Being able to create a form instance without hard-coding the form name. Ie "set frm = new Form_frmSomething" would become "set frm = CreateObject("frmSomething"). Doesn't matter how it's done, as long as I am not forced to hard-code the form name.

Anonymous said...

Temporary tables which data are specific to the Access session using the table. Ie. user A inserts a record, and concurrent user B cannot see it. Later, user A logs out and logs back in, and the record is gone. Would be extremely useful for on-the-fly data gathering for reports, and for displaying forms with transposed temporary data. Should not "bloat" the database, or I will not use it.

Anonymous said...

Bring back the help system from Access 97, which was actually useful, and you didn't dread pressing F1. I hate how the screen "bops around" when help is opened.

nwp--3fe94a said...

Hi Garry Robinson, when you have a minute, please take a look at this north wales properties offer website. This north wales properties is a lovely, family home in a coastal village of North Wales. It’s on for special discount price, that represents a 12% savings for any buyer. You have a fantastic blog here, keep it up.

Anonymous said...

The .Text property of all controls should be enabled to be an exact mirror of the .Value property.

This way, the controls in MS Access will be more compatible with the controls in VB.

Eventually, .Value in MS Access would be phased out (it would take 10+ years to phase it out, but it should happen eventually).

Anonymous said...

TRANSFORM column-name
PIVOT column-name IN (value1, value2)

There should be a way to use dynamic values in the IN clause, and not fixed literals.

Or, there should be a way of instructing the IN clause to "order" various date parts (especially textual month names) correctly (correct: Jan, Feb, Mar, Apr; as opposed to incorrect: Apr, Feb, Jan, Mar, which is what you get when PIVOTing a date by Month).

Anonymous said...

Posted: 12/15/2005

MS Access should support:

ALTER TABLE table_name
RENAME COLUMN old_name to new_name;

It is quite annoying that it returns a syntax error.

MS Access is an RDBMs, or at least it should be, and as such, it should support SQL 92 at the *very least*!

I don't know why I'm having to say this, something like this should have been in Access 95 and later; it was three years after SQL 92 at that point, and it is now thirteen years later and it still doesn't support it.

This isn't some kind of peripheral SQL 92 feature no one would use, either. It is effectively a core necessity of SQL.

Please don't make comments about using VBA or the MS Access GUI to do this. Using the GUI is out of the question (for the same reason that CREATE TABLE is a billion times superior to making a table in the GUI; and this ties in with the fact that even CREATE TABLE is not fully supported, to my great dissapointment), and writing an entire VBA function just to change the name of a column is ridiculous.

Can we just get, please, support for *most* of SQL 92? Pretty please? With sugar and cherries and candy sprinkles on top? Hello? Is there anyone at the top of MS Access development management who even knows how to write an SQL statement? Who even has to do so to make a living?

Anonymous said...

Support for:

INSERT INTO table_name
(col1, col2)

MS Access' inability to offer a realistic and professional enviornment for SQL development means that traditional SQL scripts are unavailable (unless one wishes to spend endless useless time fitting every single script into VBA string assemblies, and enormous pain in the neck, and a completely unworkable solution).

Because traditional SQL scripts are not available, this means that:

INSERT INTO table_name
VALUES(1, 2)
INSERT INTO table_name
VALUES(3, 4)
INSERT INTO table_name
VALUES(5, 6)

. . . cannot be run except to individually create a QueryDef object for each individual statement, a laughable alternative.

This is why support for:

INSERT INTO table_name
(col1, col2)

. . . would be highly reasonable.

Anonymous said...

In SQL View, when I key in CNTL-A, nothing happens.

All text should be selected.

SQL View could definitely use some superior text editing capabilities.

Anonymous said...

Better support for User mode and Designer mode.

This would include ability to "hide" (beyond the ability of the user to simply "unhide", i.e. by "hide" I mean make inaccessible by any means) the entire table, query, macro, and module object groups. Users typically do not need to see these in a completed application.

This would include the ability to hide *specific* objects in the above list, as necessary (because there are always exceptions).

Anonymous said...

I would like to see the capability to refer to recordsets directly in JET SQL on the FROM clause via VBA UDF:

SELECT T1.col1
FROM MyFunction() AS T1
WHERE T1.col1 > 1


SELECT T1.col1
FROM MyFunction() AS T1
MyTable AS T2
ON T1.col1 = T2.col1
WHERE T1.col1 > 1


SELECT T1.col1
FROM MyFunction([My Parameter 1]
,[My Parameter 2]) AS T1
WHERE T1.col1 > 1


(My apologies, as there does not seem to be a way to force the use of a monospace font to properly display aligned code elements in the examples above.)

CGG said...

Its the little things that bug me.

Surely the need for bracketing of explicit joins can be relaxed so Select is more like EVERY other database engine. Recognise SQL functions like Substring, Cast/Convert (or SQLServer-like).

Beyond improving Query editing -- Edit Query SQL in the VB editor. Also include them in global search.

franhuron1931 said...

Make no mistake: Our mission at Tip Top Equities is to sift through the thousands of underperforming companies out there to find the golden needle in the haystack. A stock worthy of your investment. A stock with the potential for big returns. More often than not, the stocks we profile show a significant increase in stock price, sometimes in days, not months or years. We have come across what we feel is one of those rare deals that the public has not heard about yet. Read on to find out more.

Nano Superlattice Technology Inc. (OTCBB Symbol: NSLT) is a nanotechnology company engaged in the coating of tools and components with nano structured PVD coatings for high-tech industries.

Nano utilizes Arc Bond Sputtering and Superlattice technology to apply multi-layers of super-hard elemental coatings on an array of precision products to achieve a variety of physical properties. The application of the coating on industrial products is designed to change their physical properties, improving a product's durability, resistance, chemical and physical characteristics as well as performance. Nano's super-hard alloy coating materials were especially developed for printed circuit board drills in response to special market requirements

The cutting of circuit boards causes severe wear on the cutting edge of drills and routers. With the increased miniaturization of personal electronics devices the dimensions of holes and cut aways are currently less than 0.2 mm. Nano coats tools with an ultra thin coating (only a few nanometers in thickness) of nitrides which can have a hardness of up to half that of diamond. This has proven to increase tool life by almost ten times. Nano plans to continue research and development into these techniques due to the vast application range for this type of nanotechnology

We believe that Nano is a company on the move. With today�s steady move towards miniaturization we feel that Nano is a company with the right product at the right time. It is our opinion that an investment in Nano will produce great returns for our readers.

Online Stock trading, in the New York Stock Exchange, and Toronto Stock Exchange, or any other stock market requires many hours of stock research. Always consult a stock broker for stock prices of penny stocks, and always seek proper free stock advice, as well as read a stock chart. This is not encouragement to buy stock, but merely a possible hot stock pick. Get a live stock market quote, before making a stock investment or participating in the stock market game or buying or selling a stock option.

mikewillis8160 said...

I read over your blog, and i found it inquisitive, you may find My Blog interesting. My blog is just about my day to day life, as a park ranger. So please Click Here To Read My Blog

Anonymous said...

Why cant Access export reports to Word? Not RTF, DOC with formatting?



Crazy Dan said...

Hi Garry Robinson, I thought I'd just leave this message on your blog. I hope you don't mind. I've been trying to find blogs where people are talking about webfilter software internet access control and when I was looking, I found this one on this post. Access 2008, thought I would say hi, before I go off to find some more webfilter software internet access control

Crazy Dan said...

Great blog. Found your blog while searching for more information at yahoo about Access 2008 . Your blog has quite a lot of interesting thoughts. Keep up the good work, Garry Robinson.

Anonymous said...

* In the Visual Basic Editor, add the ability to collapse the display of subs and functions leaving the opening line and an outlining symbol to the left (as in the Visual Studio IDE).

* Making search and replace able to be applied to apply to all queries, forms, reports and controls, not just code!

* Make it easy to hide the MS application window so you just see the open form or forms.

* A data grid control that allows images as well as data to be displayed in grid cells.

* More than four options allowed in conditional formatting.

* A combo-box property that allows you to turn off the dropdown arrow and action.

* Allow combobox and text boxes to display images/icons based conditionally on the underlying data.

* The Manifold Geographical Information System lets you store spatial polygons, lines and points in an Access table. Imagine a control in Access that could display them (ie display maps). (OK I'm a deluded dreamer on this one).

* A textbox control with a button at the right that opens the file open dialog box.

* Colour coding of SQL code in the query designer.

* extend the query designer to enable union queries to be built (perhaps with each sub-query on a seperate tab).

* Make it possible to view the full SQL code of nested subqueries in the query designer.

* Add export and import functions to the query designer that allow you to save translate SQL to and from VBA code.

Craig Allen
Forrest, Vic, Oz

Anonymous said...


1. WYIWYG report design! Yes, it is close to WYIWYG but sometimes last letter of text box is cutted, especially in 10+ words text boxes. Text box looks fine on design view, but in print preview (or when printed) last letter is sometimes cutted off.

2. Large text boxes on reports text formatting may be different than in print preview. I mean different. It appears that formatting on design view works different than for printing.

3. Considering 2) - when I need to underline some words on large text boxes on reports I place lines bellow text to imitate underlined text. As report desing differs than print preview, lines appears on place, but as the text is moved I sometimes get strike-through random text. Therefore it would be good to have tools to format text with bold, italice or underline inside one text box. Or even to use different fonts inside one text box. As is, one text box can have only one set of properties (one font, I,B,U Yes/No...).

Branislav Mihaljev

Anonymous said...

Get rid of those painful security messages about the dangers of using code ! I have stopped developing commercial apps because I am forever getting calls about my dangerous virus ridden product.

Anonymous said...

Bring back Access 97 help. Simple, precise with a few worked examples.

Anonymous said...

Get rid of the bloated size of the mdb, if all it has is code & forms without data it should not progressively grow, and should be as small as say a VB app with similar functionality.

Anonymous said...

Change the underlying construction language of reports to XML (even make it compatible with WordML). Support mixed landscape and portrait layouts in the one report. Expose more report events for greater control by code. Support the use of xsl stylesheets.

Anonymous said...

i want to design larger reports than 22 inches width. When will you go to privide that?

Anonymous said...

Provide a "wherecondition" parameter to DoCmd.OutPutTo for use when outputting a report.

Anonymous said...

Continued development of the ADP with better documentation of it.

Anonymous said...

Support of VB.Net and Framework 2.0/3.0 as an added programming language for the modules.

Anonymous said...

Something I have wanted since Access 95 is control over the color of the command button. Seems somewhat insignificant and trite but would make my forms look better.

Anonymous said...

Enjoyed the blog about find nintendo wii found it very informative. I found a good website which also features find nintendo wii and find nintendo wii. The link is great for **uk bargains** including Nintendo Wii, PS2, PS3, games consoles and features famous online stores inc Argos, Marks and Spencer, Empire Direct, LX Direct, Tesco, Next. There is also a chance to play online bingo and try your luck at the online gambling sites available inc roulette, poker and fruit machines. I've also found another site for **free soccer links**. Hope you find these sites interesting - all the best!

Anonymous said...

I would like to see a size of greater than 2 GB allowed.

Nick67 said...

Some things that I need:

1. Pay the Guatemalan who won the patent case, so that linked excel tables can be READ-WRITE again. We outgrow spreadsheets, but end-users still like the layout. It is a pain that you can't make changes to an Excel-linked table.

2. Bring back the database container. I have a 1000+ objects. A flat file listing is unacceptable. We will not migrate until this is fixed

3. Option to turn on Hungarian notation (tbl, qry, txt, lbl ect) ie txtSomeField and lblSomeField, not SomeField and Label_SomeField.

4. A wizard for importing a Word document as a report. The wizard lets you select what text will become label captions, what text will become field values in a text box, and what static text will be concatenated together with field values in a text box. The wizard then builds the query, the controls, and MAINTAINS the formatting.

5. Programmatically Export reports to PDF without needing Acrobat Standard installed (may be present in AK27).

6. Simple setting to make forms WYSWIG scale to screen resolution. Should be a property of the form, and be inherited by subforms seamlessly.

Nick67 said...

Almost forgot

7.MORE THAN 32 INDEXES on a table. My main lookup table can't enforce referential integrity on some of the one-to-many relationships because of this limit (ie main lookup table has more than 32 one-to-many relations and since enforcing RI creates an index, RI can't be enforced