Error message when opening a custom form

[Mk23]

Hi

I have an absence custom form in Outlook 2003. This form will be installed
by an add-In. It is visible at the appointment definition form. When i open
the form i get an error message "Error displaying the fields of the absence:
Invalid class string"

The form has as content an ActiveX control that set a few user properties at
the appointment.
At the environment where I have the problem is a special behavior(Perhaps it
has something to do with the problem). When I open the form Designer
Extras->Forms->Design a form select the "Lib for personal forms" and open my
form, i get a popup that wants an password.

In my opinion it has something to do with the security. Does anyone has a
hint for me, to solve this problem?

Regards Thomas

 

[Ken Slovak - [MVP - Outlook]]

A password protected form only works when in design mode, it never affects
run mode. Passwords are deprecated for Outlook 2007, they never did much
good anyway. You can always get the password of a form from its
FormDescription.Password property, which is in clear text.

It's more likely that the ActiveX control isn't being installed or isn't
being registered or is not correctly initialized, or just isn't a control
that works well when embedded within a form. Analyze the error message, what
class strings are being set, or are used to call the ActiveX control, are
they correct?

 

[Mk23]

Hi Ken

Thank for your answer.

The form I created myself and i didn't set a password. But there is now a
password required. I have this problem on only one custom pc, all the other
at the customer work correctly.
How and where do I look, that everything is correct with my ActiveX control?

Regards
Thomas

 

[Ken Slovak - [MVP - Outlook]]

Not having any idea about your ActiveX control I can't answer that. You need
to look at the instructions for that control on how to deploy the control
and how to license the deployment. I don't know if that control supports or
requires a password, so that's something else to check out.

A form password can be easily cracked if that's the problem, then you'd have
to find out who added the password and why. Since that's design time
protection it would imply that someone was customizing the form or modifying
it in some way.