I am trying to create an installation CD for my MSAccess program in
Office 2003. I used the "Access 2003 Developer Extensions". My MDE
files are installed ok, the problem is with OCX files. There is no
option for selecting them in the package program. In previous Office
version packages, OCX files where installed with setup program.

Is there any way to include them in the package program or I should
register them manually ?

"CLarkou" <clarkou@memrb.com.cy> wrote in message
news:db08d9f5.0406210154.686043bf@posting.google.c om...
[color=blue]
> I am trying to create an installation CD for my MSAccess program in
> Office 2003. I used the "Access 2003 Developer Extensions". My MDE
> files are installed ok, the problem is with OCX files. There is no
> option for selecting them in the package program. In previous Office
> version packages, OCX files where installed with setup program.
>
> Is there any way to include them in the package program or I should
> register them manually ?[/color]

I am noticing the same thing. (the calendar control seems to get installed
by the runtime anyway).

You *could* try the following:

1) include the ocx files in your list of included files

2) add the registries settings needed to register the ocx files in the list
of additional reg keys for the packager).

Of course, the above is easer said then done, as I don't know of a easy way
to get those reg settings (there is a tool out there that makes a snapshot,
and then lets you view/create the differences).

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.attcanada.net/~kallal.msn

Thanks a lot Albert.

Why Microsoft wants to make our lifes so difficult ?

Is not very easy to add the registry entries needed by OCX files. Users
may have Access 2003, so I will not install runtime. I think
MSCOMCTL.OCX is installed with Office 2003, but I need MSFLXGRD.OCX and
COMDLG32.OCX.

Anyway, I am thinking of creating 2 setups:
1. from "Office XP Developer Tools" to include only the OCX files I need
and COMCAT.DLL (version 4.71)
2. from "Access 2003 Developer Extensions" to include my 2003 MDE's.

What do you think about this ?



*** Sent via Devdex http://www.devdex.com ***
Don't just participate in USENET...get rewarded for it!

You could make/create a script that also gets installed, and that could
execute a series of regsvr32 command to register the install.

I noticed your other post about the certificates, and I am also in the
process looking for a cert.

However, in the mean time, I use the following two settings, and then get NO
nag prompts. (so, until I get the cert, I am using the following).

It is clean, and nice. And, until some kind of Certificate comes along, I
going to use the following settings:

Root:
Local Machine
Key:
Local Machine Software\Microsoft\Office\11.0\Access\Security
Name:
level
Value
#00000001

So, the above sets the macro security for ms-access to low. (1 = low, 2 =
med, 3 = high)

Root:
Local Machine
Key:
Local Machine SOFTWARE\Microsoft\Jet\4.0\Engines
Name:
SandBoxMode
Value
#00000002

The above sets sandbox mode to 2 (ms-access is not sandbox..but all other
non ms-access applications are).

Adding the above two keys to the install makes the runtime install real nice
as this eliminates any nag prompts when users run my applications.


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@msn.com
http://www.attcanada.net/~kallal.msn