/build/static/layout/Breadcrumb_cap_w.png

Microsoft Access 97

Version: 8

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login
Views: 8.2k  |  Created: 05/25/2004

Average Rating: 0
Access 97 has 1 inventory records, 4 Questions, 0 Blogs and 0 links. Please help add to this by sharing more!

Deployment Tips (5)

Most Common Setup Type
Not Determined
Average Package Difficulty Rating
Rated 0 / 5 (Not Rated) based on 0 ratings
Most Commonly Reported Deployment Method
Not Determined
119
Security
Access 97 self-registers its file associations on launch. If you also wish to install Access 2000/2002 it will replace the associations in HKEY_CLASSES_ROOT (HKLM). When Access 97 is launched in the future, it will try to re-write to HKEY_CLASSES_ROOT. If users do not have sufficient rights they will get an error when this update is attempted.

Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
6
Virtualization
If you're wanting to run Access 97 via Microsoft Application Virtualization 4.5 and later, you need to be aware that Microsoft have changed a few things in the 4.5 sequencer that break the ability to sequence Access 97. If you do use this version without first setting a reg key and rebooting the sequencer, the package will be missing a few registry keys.

HKEY_CLASSES_ROOT\Licenses\8CC49940-3146-11CF-97A1-00AA00424A9F will be missing. This will result in a "Microsoft Access can't be started as there is no license for it on this machine" error.

It will also not create any file associations (.mdb etc)

From Microsoft:

Under App-V 4.5 registry hooking moved from kernel mode to user mode. One result of this is that under 4.2 even applications that failed to have user mode hooking installed could frequently be sequenced successfully since registry settings would still be captured. If you have a 16 bit installer that you need to sequence, you need to install the user mode hooking code in this process. To accomplish this, the process must be running in its own copy of NTVDM. If it is not and instead is using a shared copy then we do not get a valid process to hook and no user mode settings will be monitored for that application.
The CreateProcess flag that controls this is CREATE_SHARED_WOW_VDM / CREATE_SEPARATE_WOW_VDM. It defaults to CREATE_SHARED_WOW_VDM. To change the default, set the global REGSZ registry entry -HKLM\SYSTEM\CurrentControlSet\Control\WOW\DefaultSeparateVDM to "yes" - on the sequencing station. You need to reboot for this flag to take effect.

Before I received the reg key fix from Microsoft, I used the old Softgrid 4.2 sequencer and that worked.

Here are the steps I took to sequence Access 97:

Start sequencer workstation (XP with SP3, no hotfixes, AV or Domain access)

Add the following reg key (needed to successfully package Access 97 in sequencer version 4.5 and later), and reboot.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW]
"DefaultSeparateVDM"="yes"

Create V:\Access.97 (we use V: instead of Q:)

Start the sequencer (I’m using 4.5.1).

Package name:
MicrosoftAccess97_MNT

Comments:

Application name: Microsoft Access 97 with SR-2
Sequencer: 4.5.1
Date: 26 March 2009
Author: Glenn Turner

Run Access 97 setup from \\app-v\installer$\MicrosoftAccess\97\setup.exe

Change installation folder to V:\Access.97.

Choose Custom installation, and select:

Microsoft Access Program Files
All Data Access components, except for dBASE and Microsoft FoxPro Drivers (we don’t use it)
Calendar Control (except Calendar Control Help)

To overcome the issues documented in http://support.microsoft.com/kb/141373:

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

From Add/Remove Programs, select Microsoft Access 97 and choose reinstall.

Click Stop Monitoring.

Leave the Add Files screen as default.
On the Configure Applications screen, delete the Office Startup application.
Check that there are file extensions under Microsoft Access. Leave the shortcut as is.

On the Launch Applications screen, highlight Microsoft Access, and click Launch.

Choose File > Open, then close Access via File > Exit. Launch one more time and exit.

As we use RTSP over port 554 in our environment, go to the Deployment tab and change the Protocol to RTSP and Hostname to APP-V. Change path to Access.97

In Virtual Registry, check that there is a key beginning with 8CC49940 under REGISTRY\MACHINE\Software\Classes\Licenses.

Save the package as \\APP-V\e$\content\Access.97\Microsoft Access 97 with SR-2.sprj


Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
5
Virtualization
If you're wanting to run Access 97 via Microsoft Application Virtualization 4.5 and later, you need to be aware that Microsoft have changed a few things in the 4.5 sequencer that break the ability to sequence Access 97. If you do use this version without first setting a reg key and rebooting the sequencer, the package will be missing a few registry keys.

HKEY_CLASSES_ROOT\Licenses\8CC49940-3146-11CF-97A1-00AA00424A9F will be missing. This will result in a "Microsoft Access can't be started as there is no license for it on this machine" error.

It will also not create any file associations (.mdb etc)

From Microsoft:

Under App-V 4.5 registry hooking moved from kernel mode to user mode. One result of this is that under 4.2 even applications that failed to have user mode hooking installed could frequently be sequenced successfully since registry settings would still be captured. If you have a 16 bit installer that you need to sequence, you need to install the user mode hooking code in this process. To accomplish this, the process must be running in its own copy of NTVDM. If it is not and instead is using a shared copy then we do not get a valid process to hook and no user mode settings will be monitored for that application.
The CreateProcess flag that controls this is CREATE_SHARED_WOW_VDM / CREATE_SEPARATE_WOW_VDM. It defaults to CREATE_SHARED_WOW_VDM. To change the default, set the global REGSZ registry entry -HKLM\SYSTEM\CurrentControlSet\Control\WOW\DefaultSeparateVDM to "yes" - on the sequencing station. You need to reboot for this flag to take effect.

Before I received the reg key fix from Microsoft, I used the old Softgrid 4.2 sequencer and that worked.

Here are the steps I took to sequence Access 97:

Start sequencer workstation (XP with SP3, no hotfixes, AV or Domain access)

Add the following reg key (needed to successfully package Access 97 in sequencer version 4.5 and later), and reboot.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WOW]
"DefaultSeparateVDM"="yes"

Create V:\Access.97 (we use V: instead of Q:)

Start the sequencer (I’m using 4.5.1).

Package name:
MicrosoftAccess97_MNT

Comments:

Application name: Microsoft Access 97 with SR-2
Sequencer: 4.5.1
Date: 26 March 2009
Author: Glenn Turner

Run Access 97 setup from \\app-v\installer$\MicrosoftAccess\97\setup.exe

Change installation folder to V:\Access.97.

Choose Custom installation, and select:

Microsoft Access Program Files
All Data Access components, except for dBASE and Microsoft FoxPro Drivers (we don’t use it)
Calendar Control (except Calendar Control Help)

To overcome the issues documented in http://support.microsoft.com/kb/141373:

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

From Add/Remove Programs, select Microsoft Access 97 and choose reinstall.

Click Stop Monitoring.

Leave the Add Files screen as default.
On the Configure Applications screen, delete the Office Startup application.
Check that there are file extensions under Microsoft Access. Leave the shortcut as is.

On the Launch Applications screen, highlight Microsoft Access, and click Launch.

Choose File > Open, then close Access via File > Exit. Launch one more time and exit.

As we use RTSP over port 554 in our environment, go to the Deployment tab and change the Protocol to RTSP and Hostname to APP-V. Change path to Access.97

In Virtual Registry, check that there is a key beginning with 8CC49940 under REGISTRY\MACHINE\Software\Classes\Licenses.

Save the package as \\APP-V\e$\content\Access.97\Microsoft Access 97 with SR-2.sprj


Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
1
Command Line
To uninstall from the command line:

\office\setup\acme.exe /w off97pro.stf /UA

\office being the path to your office installation, in my case, complete uninstall string was:

c:\access97\office\setup\acme.exe /w off97pro.stf /UA
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows
0
Note
nothing
Setup Information:
Setup Type: unspecified
Deployment Method Used: unspecified
Deployment Difficulty: unspecified
Platform(s): Windows

Inventory Records (1)

View inventory records anonymously contributed by opt-in users of the K1000 Systems Management Appliance.

Versions

Access 97

Version

8

Questions & Answers (4)

Questions & Answers related to Microsoft Access 97

3
ANSWERED
1
ANSWERS
2
ANSWERS
2
ANSWERS

Blogs (0)

Blog posts related to Microsoft Access 97

Reviews (0)

Reviews related to Microsoft Access 97

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ