J
JN
I use Office Pro 2003 to develop and Access 2003 project that most of my
company uses. Most of my users used Office Basic 2003 or Office Pro 2003
and I would deploy the Access 2003 runtime to the basic users so the could
use the app and all would work.
We just recently merged with another group that had a volume license for
Office 2003 Standard so some got moved onto our network without change and
some just got a format and reinstall of everything including their Office
2003 STD.
My Access 2003 project has forms in it that use the MSCOMCT2.OCX and
MSCOMCTL.OCX and none of the computers that have Office 2003 STD installed
are able to run the forms unless I manually register the OCX files. Both on
the move computers and the reformatted computers I have to:
regsvr32 C:\WINDOWS\system32\MSCOMCT2.OCX
regsvr32 C:\WINDOWS\system32\MSCOMCTL.OCX
Obviously I could run around to all the STD computers and run a batch file,
but I want to fix this at the source such as the install. Is there
something I can edit in the MSI file or create something like an MST file
that will register these OCX files? Are there any other files that have
been known to be missed?
company uses. Most of my users used Office Basic 2003 or Office Pro 2003
and I would deploy the Access 2003 runtime to the basic users so the could
use the app and all would work.
We just recently merged with another group that had a volume license for
Office 2003 Standard so some got moved onto our network without change and
some just got a format and reinstall of everything including their Office
2003 STD.
My Access 2003 project has forms in it that use the MSCOMCT2.OCX and
MSCOMCTL.OCX and none of the computers that have Office 2003 STD installed
are able to run the forms unless I manually register the OCX files. Both on
the move computers and the reformatted computers I have to:
regsvr32 C:\WINDOWS\system32\MSCOMCT2.OCX
regsvr32 C:\WINDOWS\system32\MSCOMCTL.OCX
Obviously I could run around to all the STD computers and run a batch file,
but I want to fix this at the source such as the install. Is there
something I can edit in the MSI file or create something like an MST file
that will register these OCX files? Are there any other files that have
been known to be missed?