Starting from Scratch

Published 28 February 06 04:21 PM

Sorry for the extra time since the last post, I got run over with some other work when I got back and am just getting through that.  Last time, we talked about modifying the issues tracking app.  This time, we'll look at starting from scratch, but again from the point of view of someone new to Access. 

Creating Schema from Scratch

Starting a new blank database in Access has always been very different than starting in Word or Excel.  In those apps, getting started goes something like "boot the app, start typing".  In Access, you've needed to know that you had to create a table to put data in, then you needed to understand data types, then you could move to the right view, then start typing.  This clearly represented the underlying structure of the database and afforded lots of control, but it was hard to understand.  With Access 12, "boot the app, start typing" works.

The default selection on the getting started screen is blank database. 

As before, you need to give the database a name and save it to the disk before continuing (our save model is unchanged).  Once the user gives the database a name and clicks continue, she's taken to a new table to begin typing.

The table works much like XL, where the top row is column names and the data goes underneath. 

Once the user has created a series of columns, she can drag / drop them to reorder.

When the user starts typing data for the first record, Access inspects the data and sets data types appropriately.  You'll see below that we've recognized the column contains a date, set the date data type in the ribbon, and provided the date picker control for the 2nd record.

If Access guesses wrong (i.e. if the user starts typing something that doesn't look like a date in the 2nd record), we'll provide UI that allows the user to change the data type or to re-enter her data.  This allows us to provide the benefits of strongly typed data to users who don't understand how to set data types themselves.

The ribbon UI provides most of the detailed data type settings in the traditional table designer, allowing the user to choose the date format.

And choose to make the column required or unique. 

The ribbon UI provides the ability to manually set the other data types as well. 

Finally, the traditional table designer is still available, providing developers or experienced Access users all the control they've had in the past. 

(Click image to enlarge)

It is easy for users to create lookup columns as well, and to roll those through the forms in the database.  Below, the user has started the Lookup Wizard to create a link between 2 tables - one for Issues and one for Contacts.  Here she selects that she'd like to present values from another table.

 

Then selects which columns to look up.

And finally she selects which to show in the table.

Creating a simple form

At this point, the schema for the database is set, and the user can begin building forms & reports.  These are available on the Insert ribbon, and here she has created a simple Issues form with one click. 

Because the Assigned To field is a lookup, the list is presented as a dropdown control with the appropriate data linked in.

Creating a Simple Report

Building a simple report is also a single click on the Insert ribbon. 

It is easy to customize the report by dragging and dropping additional fields from the Field List taskpane.  Click the image below for a more complete view. 

(Click image to enlarge)

The taskpane can even allow users to build joins without directly authoring queries.  In this example, the user is bringing in the Title field from the Contacts table, which is shown at the bottom of the taskpane.

(Click image to enlarge)

Since there are 2 potential ways to join the tables, we provide a dialog to help the user create the join.

Now the tables are both shown in the task list, and the user can drag / drop from either into her report.  Click the image below for a more complete view of the report.

(Click image to enlarge)

Next Time

Next time, we'll start taking a deeper look at Access, starting with creating schema. 

Comments

# Олег Михайлик said on February 28, 2006 11:47 PM:
Судьба офисных капризна. В то время, как FrontPage уходит с рынка, Access продол
# Frederick Grose said on March 1, 2006 12:12 AM:
It would be helpful to include an icon or symbol representing the 1:1, M:1, or 1:M relationship types on the Relationships dialog next to the word descriptions for the radio buttons.

The graphics will help the eye pick the right button more quickly and reliably.  The graphic symbol should match the symbol used in the graphical query builder or relationships map.

Perhaps the yellow, double-headed arrows between the field names could change shape to provide visual feedback on the selection made.
# Stevbe said on March 1, 2006 7:28 AM:
Thank you for the large pictures and also including the ribbon in some of them. This is very helpul to those of us not invited for Beta 1. Is that a menu I see above the ribbon in the picture showing how to manually set data types? I have read Jensen's blog about the ribbon and how much real estate it takes up but I don't remember seeing/reading about a menu above the ribbon.

It is interesting to see that after so much work was done on styling the look of Access objects that the wizards didn't seem to get the same styling attention. There is a typo in the first screen of the Lookup wizard ...
"I will_type"   I think the underscore could be dropped :-)

Can the Field List task pane be undocked /floated? I am thinking about when I am designing a report in landscape mode and I want to drag a field onto the surface that I may not be able to see any longer because the task pane forces a scroll because of docking instead of floating.

Thanks for getting back to us and I am looking forward to some deeper development blogs. Any guestimate for the release of Beta 2?, I really need to get my hands on a version I can start exploring.

Steve
# Erik Rucker said on March 1, 2006 1:02 PM:
Frederick, good thought on the icons and something we'll definitely take a look at to see if we can squeeze them in.

Stevbe, sorry I haven't been able to show the whole UI yet, but I will do so soon.  The text above the ribbon is a "tab" that lets you switch ribbons (I may even have the terminology wrong on this - Jensen's blog is the place for the real terms).  Clicking on that text replaces all the controls on the ribbon below with a different set of controls.  Again, I'll fully explain this as soon as I can.

One of the biggest challenges we ran into in Access 12 was figuring out what not to do.  If we had focussed on everything equally, none of the improvements would have been that significant since there's so much surface area in the app.  One of the things we didn't do was a lot of polish work on the wizards, so they do look a little old-school.  But - not so old school that we should be shipping typos!  Thanks for pointing that out.  

The field list will dock to the right (default for left-to-right languages), the left, or it can float.  It can't dock at the bottom because it is so tall it would be very hard to get enough rows to be useful.  Making it float, though, will achieve what you're looking for.

Beta 2 is coming along nicely, but I don't have a date I can share at this point.  I can say, though, that we're on track to ship a quite solid beta 2 and are as excited to get it out into the world as you are to have it!
# Johannes said on March 14, 2006 7:48 AM:
One question that maybe off topic:
Will you release a Access 12 Runtime?
If yes: An annoying thing in all past Access versions was, that one couldn't influence the way the Access main window and other windows popped upped in maximized mode. If your app had eg. a main window and you wanted to have the Access main window maximized and also the apps main window maximized within the Access main window, the only trick to adress this problem was to use the Win API. But there were still problems as: Does a Command Bar pop in too late? If yes, then there was some trouble with maximized windows without scroll bars and so on.
In other words: I would be glad to hear something about a more precise window positioning system. I guess that a lot of developers share my experience with past Access versions.
# A discussion of what's new in Access 12 said on March 14, 2006 6:17 PM:
One of the most basic tasks in Access is creating somewhere to put data - designing schema.  My...
# A discussion of what's new in Access 12 said on March 23, 2006 1:50 PM:
At long last, I can show and discuss the new Ribbon UI in Access 12.  There have been a few comments...
# A discussion of what's new in Access 12 said on March 24, 2006 6:04 PM:
In yesterday's post, I skipped the design view of the ribbons for all the objects simply to save space,...
# A discussion of what's new in Access 12 said on April 5, 2006 3:58 PM:
Access 12 has a variety of tools designed to make it both quicker and easier to author applications. ...
# Shrirang Moghe said on June 14, 2006 8:00 PM:
We have our cross-sections stored in a mdb file and use ODBC to read them. Now we are porting our application to 64-bit and we heard rumours that reading access database in a 64-bit process WON'T work.

Can anyone comment on this?
# Gregfls said on June 19, 2006 4:42 PM:
http://rfqrbrsfewqfw.host.com
<a href="http://rfqdbrsfewqfw.host.com">desk3</a>
[url=http://rfqsbrsfewqfw.host.com]desk4[/url]
[link=http://rfqabrsfewqfw.host.com]desk6[/link]
# Dating said on May 31, 2008 2:40 AM:

Sorry for the extra time since the last post, I got run over with some other work when I got back and am just getting through that. Last time, we talked about modifying the issues tracking app . This time, we'll look at starting from scratch, but agai

# Weddings said on June 6, 2008 3:18 AM:

Sorry for the extra time since the last post, I got run over with some other work when I got back and am just getting through that. Last time, we talked about modifying the issues tracking app . This time, we'll look at starting from scratch, but agai

New Comments to this post are disabled
Page view tracker