31 July 2007

Real World Access (31)

One of a series of articles about where Microsoft Office Access applications have found a real-world niche.

 Brent Spaulding's Processes

Maintenance/Production/Quality Management System

  I work for an automobile company in the body weld department of an assembly plant.  Our department's end product is the shell (body) of a vehicle all welded up.

To perform this task, we employ the use of several manual and automated welding processes.  The automated processes are made up of processing lines.  Each line has stations (or cells), each station typically a grouping of robots.  The robots primarily perform welding tasks.  However we also have robots to apply sealers, and move parts and vehicles from line to line or station to station.  All the robots, lines, cells, fixtures, etc are the "Processes" we use to build the product.

I have developed a Microsoft Access application, known as MxP, with a SQL Server data store, to monitor processes' status (Running / Not running), track quality issues the processes create in the product, and keep tabs on process maintenance (both preventative and reactionary).  The system is also used to provide production information (start and stop times, production quantities, efficiencies, part traceability, etc.).

Integration with an HMI (Human Machine Interface) allows me to track live information about the processes (build quantity, running status, and part traceability).  By using auto logged information, the core aspects of the data are quite accurate due to the removal of much of the user inputs.

Users input data that supports the automatically logged information.  In short, MxP will record when and where something happened, our team members record why it happened, and how they fixed it.

On top of the MxP generated data, the system also links with many other applications our facility uses for reporting and traceability purposes.

The system has the capability of filtering and sorting large amounts of information for reporting purposes and research.  The research is usually done to answer questions that generally take the form: "Which process had the most stop time due to weld separation over the last 4 months?"; "Which process had the most stop time last week?"; "When was the last time this process was stopped for >20 minutes?"… The list of questions is endless.

Because of the wide array of questions asked of MxP, the reporting system is completely flexible, in that the users have the ability to filter the data on any field for any report.

The formats of the reports range from tabular listings, detailed reports, as well as Pareto and trend line charts.  Summary reports have elements of all the different primary formatting options.

The system commonly has ~50 concurrent users, and has had a peak of ~200.  The users can access the system from our WAN which extends all across the U.S., plus has limited connectivity to Japan. 

The ultimate goal is to have one application that can provide the core information our Production and Maintenance personnel need to track and manage their day.

With the flexibility of linking with many different data sources, coupled with the ease and speed of application development and distribution, Microsoft Access has fulfilled our needs beyond the expectations of many.

25 July 2007

Real World Access (30)

One of a series of articles about where Microsoft Office Access applications have found a real-world niche.

 Leigh Purvis's Duty

Each year in the UK there are two million 8 page forms (with a possible 232 questions and potentially an additional 99 x 70 questions per form) submitted to the government for Stamp Duty Land Tax (the tax charged when buying property, which is filed by solicitors on behalf of their buyer clients).

This nets the government some £7 billion per annum.  But the old legal paper based system can require much to and fro, with late fines for firms unable to correctly submit forms in time (not to mention the embarrassing letter from the Revenue sent to the client informing of the firm's failure!)

In 2005 the government developed their own online submission process – and opened the process to third party software submitters too.

The result is a multi-user, very multi-firm Access 2003 desktop application with Jet backend, which I developed and now maintain for the owner company SDLT.co.uk.

It initially validates the user entered / imported data through the substantial set of business rules.  Upon successful local validation, the application submits a post of XML data to the online process of the Government.

Progress is polled repeatedly until a response is received indicating the success of the submission (usually well within a minute).  The result is that a user can close out a legal process in minutes which can take weeks to complete on the paper equivalent.  If any issues with the submitted data are returned then they are reported to the user to amend their data appropriately and try again right away without penalty.

A sibling Access application downloads the history of use from an online location for reporting and invoicing by the owners.

SDLT.co.uk was the first external vendor application to post submissions to the new service in 2005, and is the biggest third party software vendor handling e-submissions within this process – totalling several thousand successful submissions per month and growing constantly.

Now widely distributed in many law firms across the UK, having developed in Access meant it was possible to create all required functionality and yet be first - while any required technical changes, new standards or user requests can be implemented very quickly and are distributed through an auto-update process.  There's a version under development, where the Access application will use data in a SQL Server database.

It has become a regional software award winner.

22 July 2007

Custom Toolbars 2007

 At the June meeting of the Wellington Office User Group, Peter asked a question about using Custom Toolbars in Office 2007 applications, and how this relates to the Fluent Interface (Ribbon).

I have put together a few pieces of information, as this applies in particular to Access 2007.

Toolbars as toolbars

Whereas VBA will continue to be central to the programming of Access
applications, in general, this does not apply to the Command Bars
(including Menu Bars). You can not make modifications to menu bars and toolbars through the familiar UI, this facility simply doesn't exist.
You have to create/modify them in an earlier version of Access, and then import to your Access 2007 application. Then...
1. Click the Microsoft Office Button in the upper left corner
2. Click the Access Options button in the bottom right corner
3. Click the Current Database category on the Access Options dialog box
4. In the Ribbon and Toolbar Options section select your menu bar name from the Menu Bar combo box
5. Click Ok to save and close the Access Options dialog box.
6. Close your database and then reopen. Viola! No Ribbon, and your
custom Command Bars are shown as such.

Some more information here.

Customising the Ribbon

When it comes to controlling the Ribbon itself in Access 2007 applications, we are basically talking XML, not VBA.

Access MVP Oli Stohr has an excellent article on creating custom ribbons.

On the MSDN site, there is a community article and associated video about adding tabs and controls to the Access 2007 ribbon, which I also found very helpful.

And then, there is Office MVP Patrick Schmidt's RibbonCustomizer add-in, which is a wonderful tool for making many customisation tasks easy.

Protecting the Style in MS Word

At the June meeting of the Wellington Office User Group, Aniela asked a question about how to ensure that a Protected Document in Word 2007 can't have the Style changed.

It appears at first glance that anyone can select a different Style option from the drop-down list, even if the document has been protected and passworded.

Our presenter, Jonathan Stuckey from Microsoft has come back to us with an answer.

Thanks.

Technorati tags: ,