Aug 02

Total Visual CodeTools 2010 Ships for Microsoft Office 2010

Total Visual CodeTools for Microsoft Office 2010 for VBA and VB6FMS is pleased to announce the release of Total Visual CodeTools 2010, the most popular commercial Visual Basic for Application (VBA) and Visual Basic 6 (VB6) coding product for the Microsoft Office/Access community.

Total Visual CodeTools is an add-in that is integrated with the module editor of all VBA platforms such as Microsoft Office, Access, Excel, Outlook, Word, etc. It offers a wide range of utilities to help developers become more productive when creating new code, taking over existing projects, and delivering more robust solutions.

"Total Visual CodeTools is by far my favorite third-party product," says Alison Balter, author of Mastering Access Desktop Development, instructor and developer. "Total Visual CodeTools helps you get your job done more quickly and allows you to focus on the fun and exciting aspects of application development. My favorite feature is the Code Cleanup. If you've ever inherited a code-intensive database, you'll appreciate this feature."

Total Visual CodeTools 2010 includes many enhancements over its predecessor for Office 2007. In addition to supporting VBA in Office 2010, there are new options and better performance for Code Cleanup and Delivery, enhancements to many Code Builders including the Message Box Builder, Recordset Builder, Select Case Builder, and SQL Text Builder. New features simplify the replacement of existing error handling code, and the user interface is enhanced to support Windows 7. There’s also improved support for international languages and operating systems.

"We are very pleased to ship Total Visual CodeTools 2010," said Luke Chung, President of FMS. "This version represents our seventh major release of this product and our continued support of the VBA and VB6 developer communities."

Edwin Blancovitch of Advanced Developers in Puerto Rico adds, "I really recommend it. This tool definitely increased my productivity, allows for code optimization and quality, and best of all reduced my costs."

"I really love Total Visual CodeTools," said Peter Weinwurm of Axium Canada. "I am completely blown away by how much the products in the Total Access Developer Suite can do, and how much time they will save me."

Product Information

Total Visual CodeTools supports all Visual Basic 6.0 and VBA development environments including all versions of Microsoft Office from Office 2000 through 2010. Additional information is available on these web pages:

Licensing and Pricing

Total Visual CodeTools is available via ESD and also comes with a professionally printed 164 page user manual and CD.

Total Visual CodeTools is licensed on a per developer basis. A single license is $299. Existing customers can upgrade for $199. It is also included as a standalone product and is part of the Total Access Developer Suite, Total Access Ultimate Suite, and Total Visual Developer Suite.

Total Visual CodeTools can be purchased directly from FMS, corporate resellers, and international distributors. All FMS products include a 30-day money back guarantee.

Press Release

Jul 20

Microsoft Access 2010 Service Pack 1 VBA Project Compatibility Issues

Microsoft released service pack 1 (SP1) of Office 2010 late June 2011. Information on the update and download instructions are in their Knowledgebase article 2460049. The KB article was last updated yesterday.

Unfortunately, we and some of our customers have encountered problems after installing the update. While we haven't had exhaustive testing with SP1 and tentatively believe everything is okay with the 32 bit version, there are definitely compatibility problems with the 64 bit version of Access 2010. In particular, ACCDE files created in the original release of Access 2010 64 bit no longer run under SP1. This error message appears:

The database cannot be opened because the VBA project contained in it cannot be read. The database can be opened only if the VBA project is first deleted. Deleting the VBA project removes all code from modules, forms and reports. You should back up your database before attempting to open the database and delete the VBA project.

Obviously, with an ACCDE file, unlike an ACCDB file, you can't modify the VBA project. It requires rebuilding the ACCDE from SP1.

So far, we have not experienced problems with our 32-bit ACCDE files between the original and SP1 Access 2010 versions. Some of these issues have been noted in these articles:

This is a Microsoft KB article discussing the problem which impacts ACCDE, MDE, and ADE files created with Access 2010, 64-bit. For us, when we create MDE and ADE files for use across multiple versions of Access, we've used Access 2003 so that still works fine. The only time we use Access 2010 64-bit version is when we're creating an ACCDE specifically for Access 2010 64-bit users.

This issue impacts two of our products' Access 2010 64 bit versions:

We have created new builds of these products and are undergoing internal testing and QA to verify they work with SP1. When ready, we'll release free updates of these products to existing customers. If you need it earlier, please contact our support team. Note that this does not impact the Access 2010 32 bit version.

Regardless of whether you are using our products or not, please be aware of the compatibility issues if you're using the 64-bit version of Access and deploying ACCDE files. You will need to make sure your Access version is in sync with your users' version. Unfortunately, this bug occurs before any of your code can run to provide instructions to your users or offer a graceful exit.

Not sure what version you have installed? Run Access, select the File menu, and click on Help. The version informing is shown on the right side and will show (SP1).

Jun 01

Published on Enterprise Features: Microsoft Access Is Underrated–Your Hatred of Access Is Largely Unjustified

Microsoft Access Enterprise Features Microsoft Access

The Enterprise Features web site highlight’s FMS President Luke Chung’s discussion about why¬†Microsoft Access is underrated and hated in large enterprise organizations. “Haters Gonna Hate”

He discusses the dynamics of IT departments in large organizations and their natural conflict with the needs and budgets of information worker. He also shows how organizations that understand the strengths and weaknesses of Microsoft Access can leverage its power for competitive advantage, and how to structure service levels to do so.

Mar 30

Using Terminal Services and RemoteApp to Extend Your Microsoft Access and other Windows Applications Over the Internet

Terminal Services RemoteApp and Microsoft AccessRead our new paper on using Terminal Services and RemoteApp to Extend Microsoft Access and Other Windows Applications Over the Internet.

One of the features of Microsoft Windows Server that is increasingly popular over the last few years is the Terminal Server and more recently RemoteApp. With few exceptions, most Windows applications work within a Terminal Server environment. By doing so, your investment in existing applications, and the power of Windows desktop features and interoperability, can be exposed over the Internet.

This is particularly powerful for database applications such as Microsoft Access since it eliminates the need to send large amounts of data over the Internet for Access to process and users do not need to install Access on their machine. With RemoteApp, you can set up a terminal server experience where your users can only run your application without running other applications or browsing your network. Easily web enable all your desktop applications.

May 11

Avoid Using DoEvents to Wait in Microsoft Access, VBA, and VB6

In our Microsoft Access, VBA, and VB6 programs, we often need to pauseprocessing for a certain period of time, or until a specific time, and thencontinue processing. One common way to do this is to use the DoEvents function in a loop whilewaiting, however, this method consumes the CPU time and slows down the PCconsiderably. This is a significant problem when pausing for more than a coupleof seconds, when users will notice the slowdown. Use the Sleep command instead.

Learn more about our royalty-free MicrosoftAccess/VBA/VB6 module code.