App-V: Here’s an example of “don’t do that – but if you must, here’s how.”

Here’s an example of “don’t do that – but if you must, here’s how.” Access 97 and the Access 97 run-time module is no longer supported by Microsoft. Therefore, custom applications that use the Access 97 run-time module are also technically unsupported. Virtualizing it with App-V does not change that fact although the isolation has led to some unintended positive consequences. Always remember that it is still a risk to use App-V in this manner as future releases and patches cannot be guaranteed to be regression free in terms of how it will affect an unsupported technology.

However, if you insist on sequencing an application that uses it, the following can be done to allow you to sequence Access 97 Run-time modules in versions 4.5 or later:

First, the registry key:

HKEY_CLASSES_ROOT\Licenses\8CC49940-3146-11CF-97A1-00AA00424A9F will be missing. This will result in a license error.

To rectify this, add the following registry entry

• HKEY_CLASSES_ROOT\Licenses\8CC49940-3146-11CF-97A1-00AA00424A9F
• [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW]
  “DefaultSeparateVDM”=”yes”

This must be done and rebooted on the sequencer prior to the start of sequencing.

Install to a Mount Drive during sequencing

Upon completion of the installation, DO NOT STOP MONITORING.

Open a command prompt rename %WINDIR%\fonts\hatten.ttf to hatten.xxx

Launch Application again.

Click Stop Monitoring.