Total Access Statistics is the most advanced data analysis program for Microsoft Access. It extends the power of Microsoft Access queries with a wide range of statistical calculations including percentiles, frequency distributions, correlations, regressions, rankings, running totals, financial cash flow analysis, data normalization, crosstabs with Chi-Square, t-Tests, ANOVA, non-parametrics, probabilities, and more.
Total Access Statistics is now available for Microsoft Access 2013. Total Access Statistics 2013 includes many enhancements since the prior release of Total Access Statistics 2010:
Support for the 32 and 64 bit versions of Access 2013 with separate add-ins for each
New redistributable runtime libraries to support Access 2013, 2010, 2007, and 2003
Support for Windows 8 (and all Windows versions supported by Access)
Improved performance when analyzing large data sets
For Percentiles, when assigning percentile values to a field in your table, you can specify calculations such as quartiles, quintiles, octiles, deciles, etc. rather than just percentile
Field format is set to Percent for percentage fields in the Frequency, Crosstab (when percentages are in columns), and Chi-Square details tables
When tables are generated from the add-in, the field column widths are resized to show the entire field name and data
This error occurs in a Microsoft Access database that seems to work fine on every other machine but one. The MS Access database actually loads and runs, so the code is compiled and functional. Then it dies on some very common code such as CurrentProject.Connection for ADO to open a table or query recordset:
The “Class Not Registered” is very confusing. It implies code that won’t compile or broken library references but that’s not the true cause. Is the Access database corrupt? No.
Total Access Emailer is the most popular email automation program for Microsoft Access. It simplifies the sending of personalized emails with Access data and reports to everyone on your list.
Total Access Emailer is now available for Microsoft Access 2013. Total Access Emailer 2013 includes many enhancements since the prior release of Total Access Emailer 2010 and the Version x.6 for pre-Access 2010 versions:
Enhanced setup for Windows 8 and 64-bit installations
Supports differences in VBA code between Microsoft Access 2013 and 2010
Improved support for linked tables in SQL Server and Access databases including situations when connections are lost
User interface improvements to better manage editing and duplicating email blast specifications
Professional Version VBA library detects if the user’s machine has not run the runtime distribution EXE
Improved display of record counts for repeating multiple email blast broadcasts
The Microsoft Access team has released videos of their presentations at the SharePoint Conference from Las Vegas, NV.
With Access 2013, Access web solutions are hosted in SharePoint and rather than using SharePoint lists as they did in Access 2010, they use a real SQL Server database hosted in SQL Azure. The database can also be linked from desktop copies of Access to create hybrid solutions that serve both the web and Windows.
The Microsoft Access program managers presented these four sessions:
Don’t Forget System Administration for Microsoft Access Database Solutions
A professional Microsoft Access database application needs ongoing system administration. It’s an area that many MS Access developers neglect and causes problems when things go wrong (database corruption, missing backups, disaster recovery, etc.):
Microsoft recommends periodic database compacts and repair to maintain optimal performance and avoid database corruption.
Enterprise Quality System Administration with Audit Logs and Email Alerts
Total Visual Agent has provided an Enterprise Quality solution for almost 20 years by giving organizations a reliable way to perform their critical tasks on a 24/7, 365 days a year basis. A detailed audit log documents each action that is performed, and sends emails if errors are encountered.
Schedule Events, Databases, and Actions to Perform
Total Visual Agent automates and schedules Microsoft Access tasks. It ensures repetitive tasks are completed reliably. Tasks such as database compact and repair, zipped backups, rolling backups (e.g. 7 copies for each day of the week), running macros, running Windows command lines, making copies of table data, collecting database statistics such as size and record counts, etc. Easily schedule tasks for the middle of the night and know they’ll be completed.
Events can be scheduled every X minutes, hourly, daily, weekly, monthly or just one time. You can specify the days of week and time periods that it runs to limit processing to off-hours. Select the databases and directories (including subdirectories) to manage with support for workgroup security and database passwords.
Includes a Windows Service for Secure Processing and Reliability
Once defined, the events and tasks can be run by our Monitor program that is a standard Windows program.
Alternatively, Total Visual Agent includes a Windows Service, so you can run your tasks without having anyone logged on the machine. The Windows service is a more secure, robust solution since it can automatically restart if the machine reboots.
New Features in the 2013 Version
A huge number of new features were added in this 2013 release from the previous 2007 version:
Support for Microsoft Access 2013 and 2010, plus 2007
Support for 64 bit Operating Systems
Simplified Startup and Easier Management of Multiple Microsoft Access Versions
Import Settings from Multiple Versions of Total Visual Agent
Test All Actions for an Event, Database, Directory or Task Group
Create Events that Run Every X Minutes
Create Events that are Limited to Periods Spanning Midnight
Process Directories with Managed Databases
Data Extract Tables are Keyed
Run Macros for Database Password Protected Databases
Pause for a Fractional Minute
Compressed Archive File Names Support Multiple Extensions
More Detailed Activity History Log with Deletions
More Detailed Database Statistics with Deletions
Add Your Comments to Events, Directories, and Actions
The Microsoft Access 2013 Runtime enables you to distribute Access 2013 applications to users who do not have the full version of Access 2013 installed on their computers. The Microsoft Access 2013 Runtime Download is available in 38 languages!
Note that due to the many deprecated features in Access 2013, we would recommend developers to stick to the Access 2010 runtime version unless you’re deploying to an environment that has already migrated to Office 2013.
The National Archives and Records Administration (NARA) is the record keeper for the United States. Of all documents and materials created in the course of business by the United States Federal government, only 1%-3% are important enough for legal or historical reasons that they are kept by NARA forever.
To ensure the quality of work performed by their Facilities Management service providers, the National Archives and Records Administration performs both random and targeted inspections of completed work orders.
Inspection findings were documented on paper, which ironically, wasn’t efficient for the NARA. Reports were manually created to generate the service results. This manual process was time consuming and prone to human error.
FMS was selected to create a professional, multiuser system to collect the inspection results electronically and generate a variety of management reports.Within two months, we deployed our solution which offers data entry screens to replicate a variety of existing forms and many new management reports. An intuitive user interface made it easy for users without requiring extensive training. More importantly, we established a solid database foundation to improve NARA processes both today and into the future.
Stores inspection results into a shared database
Increases efficiency and accuracy of the collection and reporting process
Gathers information and performs statistical analysis in ways that were previously not available
Our Professional Solutions Group was recently asked to diagnose a Microsoft Access database experiencing recurring compile errors with code behind a form that looks like this:
If IsNull(Me.Comments) Then
where Comments is not a control on the form, but a field in the form’s RecordSource.
In general, this compiles and runs fine, but on seemingly random occasions while the program is running, it generates a compile error saying that that field was not found. But the field always existed on the form’s RecordSource, so why was this happening?
There are a few ways to avoid this problem:
Change all the Me. to Me! which is the proper way to reference a field in VBA code, if there is no control bound to this field.
Create an invisible text box that assigns its ControlSource to that field, give the text box a different name (e.g. txtComments), and reference the text box in code.
Deploy the database so its compiled state cannot be changed (ACCDE or MDE)
We prefer the use of the invisible text box so that we can reference the control name via the “Me.” syntax rather than “Me!”. The “Me.” syntax is verified when the code is compiled so that a typo with the control name is caught. This is preferable to a runtime error that gets triggered when the user encounters that line of code.
Though we knew how to fix this, we were curious to understand why the compilation wasn’t consistent across users. It also didn’t fail when a specific event occurred. It seemed almost random when the compile error arose. And the form triggering the error seemed perfectly fine with a reference to a field that exists in its RecordSource.
The Real Cause for the Compile Error
Through our own research and help from our Microsoft Access MVP colleagues, we discovered that the compile error was tied to programmatically changing the RecordSource of a form. The change is not necessarily on the form where the compile error is triggered.
Microsoft Access seems to reset its internal list of field references some time after the RecordSource is modified, which triggers the compile error. This explains why some users experienced it and others did not since it depended on whether the user opened a form that changed its RecordSource. It also explained why the error didn’t occur immediately after a RecordSource was modified.
Special thanks to Dirk Goldgar for pointing this out. Hope you never encounter this!
Additional Resources for Database Compile and Field Reference Issues