Improvements to assistance features and content in 2007

Published 04 December 06 05:50 PM

The following is a post from Marci Billow, the UA manager for Access (and other teams in Office).  The UA team has done a tremendous amount of work in improving help, and wanted to spread the word.

__________________________________________________ 

During the past few years, you shared a number of concerns and suggestions for how we might improve assistance content and features for Microsoft Office Access. Your feedback regarded two primary areas, Help functionality and content organization.

Help functionality

This includes the design of Help features such as search, the Help window, and where assistance content is stored. Common concerns were:

  • Search is not effective. 
  • Developer content is difficult to access. 
  • The best content can be accessed only when your computer is connected to the Internet and, consequently, Microsoft Office Online. 
  • Sharing articles with others is too difficult. 
  • The Help task pane and window is difficult to manage, especially in combination with the application window. 
  • Printer-friendly versions of articles aren’t available.

Content organization

This includes the way that articles complement each other and how information is distributed within and across articles. Common concerns were that reference information about functions, properties, and related programming options and component technologies is difficult to find, and information within specific sets of content is too distributed to be useful. You asked for one-stop shopping for all Access content.

We listened to your feedback and we redesigned Help features and content to address as much of your feedback as possible. In the following sections, you’ll find details about many of the improvements to assistance features and content in the 2007 Microsoft Office system.

Searching for content

In the Office 2007 release, you’ll find that search has improved significantly. Full-text search is now available; the search feature indexes and searches every word in an article. This means that searching for an exact phrase or word that you’ve seen in the title or body of an article ensures that the article appears in the list of search results. In addition, search automatically tracks and, through aggregation and analysis, moves articles up in the list of search results when people more frequently select those articles from the search results for a given search keyword. In reviewing the preliminary data, we have seen a significant improvement in the search results, as measured by the number of times people select an article from a list of search results compared to not selecting any articles from those results.

Accessing developer content

Developer and other types of content continue to be distinct sets of content in the Office 2007 release. However, you can now access developer content from any area of the program without opening the Microsoft Visual Basic Editor (VBE).

By maintaining developer and other types of content as distinct sets of content, we ensure that each set of content has the appropriate breadth and depth for each person’s goals. We help ensure, for example, that people don’t incorrectly assume that they must understand VBA to implement a database solution successfully. Combining all of the developer and other types of content into a single set of content could imply otherwise.

For cases where quick and easy access to developer and other types of content is useful, we added a Search menu to the Help window. You can use that menu to access the Developer Reference, Access Help, and other types of Access content from the same place, regardless of the feature that you are currently using.


Use the Search menu to switch to a specific set of content with only two clicks, whether you’re designing a form, using the VBE, or managing a connection to a Microsoft SQL Server database. For example, if you are designing a form, you can browse or search the Developer Reference. If you are using the VBE, you can browse or search Access Help. If you choose to display assistance content from Office Online, instead of your computer, you can additionally search all types of content at once; just click All Access on the Search menu. You can also limit your search to only a specific type of content by clicking the appropriate option on the Search menu.

In Office Access 2007, you can additionally:

  • Find reference information for macro actions, functions, and SQL statements in Access Help. Based on data for Office Access 2003 content, we also identified the most frequently used properties, and copied the corresponding articles from the Developer Reference into Access Help. We’ll continue to monitor the data and add more reference articles as necessary. 
  • Find content about the VBE, Microsoft Data Access Objects (DAO), Microsoft ActiveX Data Objects (ADO), Microsoft Access SQL Reference, the Access database engine, and other component technologies directly in the Developer Reference. You can find it by using search or the table of contents.

Accessing content, online versus offline

When we released Office 2003, we committed ourselves to developing and revising articles in response to feedback from you, our customers. We have always solicited and responded to customer feedback, but previously it was on a smaller scale. We were limited to discussion groups, user groups, and other types of smaller-scale forums. In addition, those forums typically emphasized features in Office programs, not specific assistance articles or all of the content about a program.

With the release of Office 2003, our goals were to:

  • Expand the feedback scale to include as many customers as possible
  • Provide customers with easy and direct ways to tell us specifically what they love and what we can improve
  • Respond to customer feedback by publishing new and revised content continuously

Office Online made it possible to achieve these goals.

It provides a repository for assistance content that you can display in the Help window, and you can share your feedback about that content with us directly.


After you click a button indicating whether an article was helpful to you, you can additionally share specific comments about that article.


With a single click and a few optional words, you and millions of other customers now tell us what you like and what you want. To date, we’ve received approximately 86 million ratings and 13 million comments for the Office 2003 content, with additional ratings and comments coming in every day from customers around the world. We know which content is viewed most frequently, which content satisfies customers the most, and what content need to be developed. In response, we review and analyze that information, and then respond to it by publishing new and revised content continuously.

We’ve maintained and extended these goals for the Office 2007 system. For example, Office Access 2007 customers asked for content about Access Data Projects (ADP). In response, we developed an article that explains how to create an ADP, and will develop additional content about ADP if customers indicate that they want more on the subject. We also implemented Help in a way that makes it possible for you to download new and revised content to your computer and use it when you can’t access the Internet and Office Online. We are now defining the plan and schedule for releasing those updates. As soon as the first wave of updates is available you can expect to see them advertised on Office Online, MSDN, and Microsoft Update.

We also added a menu to the Help window that makes it easy to switch between displaying offline content, or content on your computer, and online content, or content on the Web. To switch between offline and online, open the Connection Status menu in the lower-right corner of the Help window, and then click the setting that you want.


You can also temporarily switch to online content by using the Search menu in the Help window. Just click the arrow next to Search , and then click the set of content that you want to browse or search.

As a bonus, the Help window switches automatically to offline content when your computer is not connected to the Internet.

Sharing links to articles

Helping someone else find a specific article is much easier in the Office 2007 release. Every article has a unique identifier that anyone can use to search for and find the article. Here’s how:

  • To find the identifier for an article, right-click the article in the Help window, and then click Copy Topic ID on the shortcut menu.


  • To search for an article by using the identifier, paste or type the identifier in the Search box, and then press RETURN.

In the list of search results, click the title of the article. If you are connected to Office Online, you can use this procedure to find specific articles in any set of Access content, without first switching to that set of content. For example, if you are viewing Access Help and search for the topic identifier of an article in the Developer Reference, the title of the developer article appears. It’s not necessary to switch to the Developer Reference before you search for the identifier.

Overall, you can now share an article with colleagues easily. Simply send them the identifier for the article that you want to share. Your colleagues can then search for that identifier and view the article. Of course, you can also find the article on Office Online or MSDN and send the URL to your colleagues.

Managing the Help window

In the Office 2007 system, the Help window is a separate application and window that provides one-stop shopping for finding and using content. This means that you can easily do the following with it:

  • Minimize it to the Microsoft Windows taskbar and display it again when you need it
  • Move and resize it, and have it appear in the same position and at the same size during subsequent Help sessions
  • Display it in front of or hide it behind the application window by pressing ALT+TAB, clicking the taskbar button in the Windows taskbar, or by using Windows Task Manager
  • Open the window when a dialog box is open by either pressing F1 or clicking the Help ? button in the title bar of the dialog box

In addition, there is a distinct Help window for each Office program, so you can open Help for more than one program at the same time.

Printing articles

Office Online now provides a “printer-friendly” view of each article.

The view excludes distracting, navigational elements of the site.

 

A link to this view appears in the upper-right corner of every article. Simply click the link to display a version of the article that contains only the content of the article, and then print that version of the article.

Navigating and using Access Help and the Developer Reference

We improved the content in additional ways that aren’t mentioned above. For Access Help, the articles are less “fragmented.” Rather than distribute content across multiple articles, each article has all of the key information in one place whether it be conceptual, procedural, or troubleshooting information. What might have been five distinct articles in Help for Office Access 2003 is likely to be a single article in Help for Office Access 2007.

For the Developer Reference, we considered feedback from Office customers in combination with Visual Studio customers and made these additional improvements:

  • Articles use the same design as articles in Microsoft Visual Studio 2005 Help and other Microsoft development technologies.


  • Class library, or object model reference, articles are organized the same way as class library articles in Visual Studio Help; property, method, and event articles are classified under the objects to which they are scoped, rather than in alphabetical categories that don't clearly represent the relationships between objects and their members.


  • Class library references include member table articles. These articles provide both a summary of the members of objects in the object model, and links to articles about corresponding members.


  • Conceptual articles focus more on specific tasks and goals, or “How do I?” information, as is the case with Visual Studio Help. These articles explain how to accomplish specific goals, scenarios, and customization tasks.
  • A conceptual framework is available and makes it easier for both novice and experienced developers to understand Access as a development platform.
  • Additional, task-based code samples are available and more code samples will be added in response to customer requests for those samples.
  • All content is published continuously to both MSDN and Office Online, and we will improve it continuously in response to your feedback. By publishing new and revised content to Office Online, we ensure that you can access the best and latest content from within the Help window.

Overall, your feedback had a tremendous impact on the design and implementation of the assistance features and content. Thank you for sharing specific concerns and suggestions. You definitely made a difference.

Marci Billow
Content Manager

Filed under:

Comments

# Rod Stevens said on December 4, 2006 8:12 PM:

The proof of the pudding will be in the eating...

Oddly, I still find MS Access 97 help to be far more effective than anything released since.  Sure it lack some bells and whistles but it was simple and worked.

So I really hope the new help system actually works for us and  not against us...

Here's hoping...

# HelpPlease said on December 5, 2006 9:53 AM:

I have a question in regards to Access 2007 and ADO (msado15.dll).  I have an appplication that reads information from Access Database, it uses ADO (msado15.dll) to open a database using Connection15::Open( ). I am unable to open Access 2007 database using this method. I get the following error: "Microsoft JET Database Engine, Unrecognized database format". Is there something I am doing wrong or I should be aware of? Does msado15.dll support Access 2007 databases? Thank you in advance.

# Neil Black said on December 5, 2006 1:18 PM:

Regarding the question on using ADO to read an Access 2007 database:  Just change your OLEDB connection string to read "Microsoft.ACE.OLEDB.12.0".  This will use the new Access database engine OLEDB driver, which can read Access 2007 (as well as previous format) files.  Jet, which was used in previous version of Access, cannot read Access 2007 files.

# Tim said on December 5, 2006 6:25 PM:

Erik:

Your team has done a great job for improving Access. I manage hundreds of Access database for our national park. I was worried that Microsoft will not support Access database anymore. If Access will not be available, the only option for us is to use Filemaker. Thanks for your service. Most researchers in our park are not programmers. They also want to control their own data. They do not like work on SQL Server or Oracle.

# Jeff said on December 13, 2006 4:42 PM:

Your pictures aren't loading on any of your blog articles today.  Looks like the pictures are located at:

http://clintc.officeisp.net/Blogs/2006/

and it seems to be down........

# clintc said on December 14, 2006 11:48 AM:

Thanks for the comments Tim.

Jeff, the site hosting our images was down yesterday. Everything should be back up and running.

# TimS said on December 14, 2006 8:38 PM:

Clint:

Are there going to be more posts?

# clintc said on December 15, 2006 2:49 AM:

TimS,

Good question. I have been posting a bit these days on my blog at http://blogs.msdn.com/clintcovington. Overall, Erik and I have been extremely busy these days planning Office 14. This happens to be our most critical time in the cycle when it comes to influencing the direction of the product. You likely have noticed a slow down in all the Office blogs these days as people are heading out on vacation for the holidays but if they are in the office--it is all about strategy planning.

Erik and I talked today about posting some links to papers that were recently made available on MSDN but I'm not sure when Erik leaves for vacation.

# grovelli said on December 18, 2006 3:47 PM:

How come you're planning on shrinking the size of the files down to 1 from 2 GBytes?

What would one be supposed to use instead of continuous forms and combo boxes?

# StepUP said on December 18, 2006 4:07 PM:

This ia a BIG JOKE......

right??

# grovelli said on December 18, 2006 4:22 PM:

Come to think of it, I think StepUp is right, considering Erik's leapfrogged version 13. Got me this time Erik; to my excuse I bring the fact that we're still well away of April 1st :-P

# Erik Rucker said on December 18, 2006 6:07 PM:

The feature list I supposedly posted was posted by someone else.  So, yes, I guess it was a big joke, but the jokester wasn't me.  Thanks to whoever for the list of features, but it turns out those aren't quite the ones we're thinking of.

I've removed the impostor post, and sorry for the confusion.

    Thanks,

          Erik

# Zen said on December 19, 2006 7:47 AM:

Grovelli:

"How come you're planning on shrinking the size of the files down to 1 from 2 GBytes?

What would one be supposed to use instead of continuous forms and combo boxes?"

StepUP:

"This ia a BIG JOKE......

right??"

Me:

However it seems that with Access 2007 they have made something of similar: no replication, no MDW protection, no MenuBars, no DAPs, little support for ADP projects...

ACCESS 14:  I'm shivering   :-)

Bye

# StepUP said on December 19, 2006 12:47 PM:

Right Zen.

I really hope that when the next version (BTW..it IS 13 and not 14...right? Or are they skipping unlucky 13? I think it might actually be LUCKY to use 13) starts to get developed, they actually get AND USE some feedback from real developers.

This version is such a hack for developers that I'm hoping there will be some kind of recovery in the next version.

In the meantime, I'm writing an Access-like template in VB.Net.

# Jim said on December 20, 2006 8:01 AM:

Zen/StepUP - give it a rest! You guys are sucking the life out of this blog. Every time Eric sticks his nose around here a few of you guys feel compelled to bloody it over the SAME issues. Why do you think he doesn't post any more? You guys keep banging on and on about the same things sucking anything positive out of it.

If you do feel compelled to continue to bang on and on, at least do it with a balanced perspective.

Replication is supported in MDBs but not ACCDB-that is okay everyone uses MySQL or SQL Server for new replication projects.

User level security is supported in MDB but not ACCDB-this blows but at least there isn't the illusion of security. Anyone could crack the old model for less than $25.

MenuBars are replaced by the Ribbon and XML authoring. MDBs do support them for some backwards configurations so you might need to keep 2003 around to edit them.

DAPs - good riddence. They are worthless any ways. It is about time the team starts improving forms and reports instead of wasting their time on a lame ActiveX web technology.

ADPs now support SQL Server 2005 but remain largely unchanged but okay most people use mdb databases anyway.

I just don't see how repeating the same list over and over is helpful--it has sucked the life out of this blog.

# Frank Kobes said on December 20, 2006 4:13 PM:

Fragmented help information has been my complaint. I look forward to using the improvements. Thank you.

# Sergei said on December 23, 2006 3:17 AM:

Integration with SharePoint services 3.0 was a little pain for me. You have to configure security on SharePoint first and it is not intuitive.

Should a user have administrative privileges to publish a database to SharePoint services?

"Collecting data via email" option does not allow you to use the existing InfoPath form.

Access 12 crashed while I was editing text in a rich text box on the form.

In Word 12 there is an option to create a workspace on SharePoint Services portal.

Why there is no such an option in Access 12?

Thank you.

# David W. Fenton said on December 27, 2006 6:25 PM:

Jim wrote:

> Zen/StepUP - give it a rest! You guys are sucking

> the life out of this blog. Every time Eric sticks his

> nose around here a few of you guys feel compelled

> to bloody it over the SAME issues. Why do you think

> he doesn't post any more? You guys keep banging

> on and on about the same things sucking anything

> positive out of it.

>

> If you do feel compelled to continue to bang on and

> on, at least do it with a balanced perspective.

A2K7 is shaping up to be a disaster on the order of the introduction of A2K -- not quite as bad as A95, but a disaster nonetheless. Here's a preliminary assessment:

http://allenbrowne.com/Access2007.html

That's some pretty major stuff, and remarkably problematic in a whole host of ways. Of particular interest to developers is this problem on Windows Vista with running multiple versions of Access:

From Allen Browne's website:

> There is another serious bug running multiple

> Access versions under Windows Vista Ultimate.

> Instead of using the correct library for each

> version, the Access library gets jammed on

> Microsoft Access 12.0 Library, which renders

> the previous versions unusable, so you are

> now stuck for editing in previous versions or

> releasing MDEs for your clients. (This appears

> to be a problem with the registry in Vista, i.e.

> Windows XP handles multiple versions correctly.)

Is that not a pretty serious bug?

> Replication is supported in MDBs but not

> ACCDB-that is okay everyone uses MySQL or

> SQL Server for new replication projects.

Speak for yourself, cowboy. Jet is still completely viable for a lot of small businesses, and server databases are not justified, especially for laptop users. Nobody who has any real experience with Jet Replication would make such a statement. It's far easier to implement a replicated Jet app on multiple machines than it is to install and administer SQL Server on multiple machines. And MySQL for replication? Hello? The MYISAM format doesn't support anything but master/slave replication, and the InnoDB tables don't support full merge replication like Jet has done for over 10 years.

> User level security is supported in MDB but

> not ACCDB-this blows but at least there isn't

> the illusion of security. Anyone could crack the

> old model for less than $25.

User-level security is often not used to secure data, but to identify users. Yes, one could use Windows logons, but how does one manage user groups if you're not an administrator on the domain where your users are logged in? That wouldn't work on a peer-to-peer network without a server, anyway, which is where a lot of Access-to-Jet applications are running.

[]

> ADPs now support SQL Server 2005 but

> remain largely unchanged but okay most

> people use mdb databases anyway.

I've read that A2K3 ADPs run in A2K7 fall over and have major, major performance  problems. So, they basically don't work any more. I agree that they were never a good idea, but a huge number of people have used them (because the fake justification (i.e., "Access without Jet") for them fooled a lot of IT departments), and a lot of people are reporting absolutely HUGE problems with them.

> I just don't see how repeating the same

> list over and over is helpful--it has sucked

> the life out of this blog.

The reason is that nobody seems to be taking the developers' complaints serioiusly.

The problem in my opinion is the design of A2K7, not the developers who are using this forum to complain.

Where else do we get an opportunity to register our unhappiness about the direction of Access?

--

David W. Fenton

# zen said on December 28, 2006 7:45 AM:

Jim:

"Zen/StepUP - give it a rest! You guys are sucking the life out of this blog. Every time Eric sticks his nose around here a few of you guys feel compelled to bloody it over the SAME issues. Why do you think he doesn't post any more? You guys keep banging on and on about the same things sucking anything positive out of it"

Jim, MS Access should be a Developer Tool, a professional DB-RAD and NOT a videogame for students.

The Microsoft Access Team work on Access like a Nintendo-developer works on a game...

Bye

# David W. Fenton said on December 31, 2006 3:32 PM:

New news on the A2K7 front:

Replicated apps from previous versions of Access can't use DAO to synchronize. MS acknowledges it's broken and advises using JRO, which apparently still works (even though this contradicts their recent policy of properly deprecating ADO and its stepchildren in favor of DAO for work with Jet data). MS is talking about a hotfix, which is good, but this kind of problem shows pretty clearly that MS simply didn't think through the design of A2K7 and thoroughly test it with legacy apps. My guess is they spent all their time on the new features and the new data format and assumed that legacy apps would just work.

A2K7 is just a complete disaster.

--

David W. Fenton

# StepUP said on January 5, 2007 2:53 PM:

Yes David, I agree.

And....Just as I thought!

I just downloaded the Office 2007 trial version. I had requested several months ago that the "auto repeat" functionality in the navigation bar for records in a form or datasheet be re-instated (why it was taken out in the first place, I have no clue. Its been in Access since version 1.0).

I then requested months later..had this been fixed? Of course, no answer was given. I guess I shouldn't have been surprised that the request was completely ignored...just like all the other requests from developers were ignored all along on this forum.

Sigh.....

# grovelli said on January 6, 2007 6:16 AM:

How do you use this "auto repeat" functionality in Access 2003? I've tried searching Access Help(F1) but can't find anything.

# grovelli said on January 6, 2007 6:16 AM:

How do you use this "auto repeat" functionality in Access 2003? I've tried searching Access Help(F1) but can't find anything.

# StepUP said on January 6, 2007 10:24 AM:

By "auto repeat" I mean that records scroll continuously when one of the buttons (next or previous) is clicked on the navigation bar. This allows you to quickly scroll through records on a bound form or a datasheet.

Why in world would they disable this feauture??

# clintc said on January 11, 2007 1:14 AM:

I can give you the story about auto repeat. Shortly after beta 1 shipped I wrote a spec to update the visuals of a number of aspects of the UI to be more modern and look more consistent with the new status bar, ribbon, navigation pane, etc. The navigation bar use to have a heavy 3-d look that stood out like a sore thumb. A developer on the team ended up re-writing the control with some new technology components (the original control was built on some very old internal technology that din't support the new visuals). As part of updating the visuals we missed the auto-repeat feature.

You posted about it in this forum a while back and I went and talked to development about bring back the feature. The code was written in a way that he couldn't use the old logic to do the auto-repeat functionlity. They looked at it and determined end user benefit didn't out-weight the risk of taking a largish new code change, test the code, fix bugs new bugs, etc.  I had a hard time arguing that the feature was widely used by current customers.

I should have replied to your original but it took a while to get the final resolution to the issue.

I feel bad that the feature was missed in my original spec--honestly, I didn't know it existed until you mentioned it. We have a bug in the system and I expect it will get fixed in the next version.

David,

We haven't seen bugs entered by beta customers expressing major performance problems with ADPs. If a customer does have perf problems that are new to 2007 we certianly will take a look at the issues and likely fix it through the QFE process. So far, I haven't seen those issues...

IMO - if you look at the list of bugs Allan lists as fixed in 2007 it seems to me that the fixed issues are far more critical than the new to 2007 issues. That said, we are looking at some of the issues on his list for SP1.

New Comments to this post are disabled
Page view tracker