Total Access Analyzer is the most popular Microsoft Access product of all-time! Documenting and analyzing your database objects, macros and VBA module code, Total Access Analyzer helps you understand what's going on. Take control of your MS Access applications and find errors and ways to improve their design and performance. Over 300 issues are pinpointed with 380 presentation quality reports for comprehensive documentation and cross-referencing of your application. Winner of every Best Microsoft Access Add-in award with great reviews, Total Access Analyzer remains the "Must Have" tool for serious Microsoft Access developers and people who inherit existing Access solutions.
Here’s a response to a question about the standards we implement for our Microsoft Access applications. These are some fundamentals for ensuring a solid foundation for professional Access solutions in priority with some resources related to them:
Split Database Design. Without this, it’s nearly impossible to enhance the database while others are changing the data.
Cleaning up VBA code. From code indentations to applying our variable naming conventions along with prefixes for global vs. module vs. procedure, and constants vs parameters vs. regular variable names. We use the Code Cleanup feature of Total Visual CodeTools to do this. Personally, without cleaning it up to our standards, I find it nearly impossible to get any work done while I’m struggling with someone else’s convention.
Setting up a development, testing and deployment process so changes can be implemented safely and efficiently. Lots of issues around this but having a fast, stable way to manage changes and how people launch the Access application is critical. We use our Total Access Startup program to help with this.
After these structures are in place, we’re ready to run Total Access Analyzer against the database to address the issues it finds wrong and could be improved in the application.
Microsoft has officially designated FMS President Luke Chung as a Microsoft MVP for supporting the Microsoft Access community.
Since the official launch of Microsoft Access twenty years ago, Luke Chung has been at the forefront of the Microsoft Access community (read his impression on the day Microsoft Access debuted). He has written numerous articles, spoken at conferences around the world, and collaborated with the Microsoft Access development team over the years. His leadership propelled FMS to the world’s leading developer of commercial products for Microsoft Access with tens of thousands of customers in 100+ countries.
While there are more than 100 million social and technical community members, only a small portion are selected to be recognized as Microsoft MVPs. Each year, around 4,000 MVPs are honored. 982 were recognized on July 1, including Luke. These individuals were chosen because they have demonstrated their deep commitment to helping others make the most of their technology, voluntarily sharing their passion, and real-world knowledge of Microsoft products with the community. Candidates are rigorously evaluated for their technical expertise, community leadership, and voluntary community contributions for the previous year. They come from more than 90 countries, speak over 40 different languages, and are awarded in more than 90 Microsoft technologies. Microsoft Announcement
There are many, many legacy Microsoft Access databases that need to be supported and enhanced. Often the original developer is long gone and there’s little to no documentation available. Yet, you’re expected to take care of it.
No matter what technology it is, taking over someone else’s work is always challenging. It’s even more challenging if you become responsible for a system that you (and no one else) understands.
FMS President Luke Chung explored this topic during his presentation at the Portland Oregon Microsoft Access User Group Conference. Learn about the issues and techniques we’ve learned over the years to triage, enhance, and support Microsoft Access applications, including migrating and upsizing to SQL Server and other platforms.
TechEd is Microsoft’s premier conference for IT professionals and developers. The sold-out conference took place in Orlando, Florida last week.
If you didn’t attend, you can still watch many of the videos from the conference, including the keynotes and other highlights from each day. Visit the TechEd web site and learn about the latest in Microsoft technology.
The announcements this year are stunning with huge advances in Azure, Visual Studio .NET, SkyDrive, LightSwitch, Virtual Machines, and more.
When designing an application and its tables, it’s very important to capture the time dimension and determine how data should be stored with the expectation that it will change over time. While there’s a natural tendency to keep data normalized so that the same information is stored in only one place, the time dimension also needs to be considered.
What Needs to be Preserved Over Time?
Making Sure Data Normalization Doesn’t Lose Historical Data
FMS developer Molly Pell is a guest blogger on the Microsoft Access developer blog. This post demonstrates a neat trick that you can use to filter a Continuous or Split form while your users are typing in a Combo Box.
There are many things a user does with an application that need to be preserved either during processing, between screens, between sessions, or between application updates/versions. When designing a system, it’s important to consider what needs to be kept and where/how to do this. If designed properly, the data should also support multi-user environments.
Users are commonly annoyed to be forced to re-enter their last specifications when the application should start with that as its default. After all, a computer is supposed to be good at remembering things, right?
There are several ways to preserve user information during a session, on a PC, and/or between PCs:
Keeping Selections in Memory for the Current Session
Using the Registry to Store User Information Between Sessions
Using Private Tables to Store Information Between Sessions
To use combo boxes effectively, learn about the following properties:
* LimitToList: Set this property to Yes to prevent values that are not in your list. * AutoExpand: Set this property to Yes to automatically select a matching value in the list as you type. * ListRows: Set this value to a high value so that the drop down shows as many list items as space allows.
On a form with multiple ComboBoxes, you may want to make the selection in one ComboBox limit the choices in another ComboBox. To do this, add code to the “AfterUpdate” event of the first control that updates the RowSource property of the second control.