Outlook Form does not prompt for macros

[alohrer]

I know the subject is a little deceiving but here is my problem. We
have a form that is published in the Organization Library that users
will then Publish to their Personal Library. The macros/vba code runs
fine when they open it from these Libraries. This application is used
by our field service people, so often times they will fill out most of
the relevant information and then save it to their drafts. They are
accustomed to then open it from their drafts and click on the Enable
Macros button in the Security Warning. However, recently, they
stopped receiving this warning and it's not allowing the execution of
the code. I know these are considered "One-off" forms and I've made
sure that the check box for sending the form defenition is NOT checked
when they publish the form.

We've checked the Exchange Security Templates and they all have the
settings for running Macros to prompt.

Does anyone have any ideas? I've tried everything.

 

[David Tongeman]

There's not quite enough info for a full response. But I can't help wondering
why you are setting it up the way you are. Its not clear why you need the
form saved at organizational forms as well as personal forms level.

It sounds like you are using a message form to save information. You might
be better using a custom task form or a contact form in a public folder to
store the information. THis would make it much easier to save unfinished
versions of the form. (You just save it in the folder and re-open it to add
he remaining information).
You could even have a button on the task form which created a message with
all the relevant information in the body and sent it to the right place. They
could use this when the information was complete.

If you need to send field engineers basic information, you could store the
initial information in the custom task form in the public folder, and send a
link to that task in an email to the field service people.

Either way I would have thought avoiding one off forms was highly desireable.

 

[Ken Slovak - [MVP - Outlook]]

Form code has nothing to do with VBA macro code. Form code won't run in an
unpublished or one-off form but that again has nothing to do with the macro
warning or VBA code.

You should never publish a form in more than 1 place, that's a bad thing.

Macro code runs from the VBA project, not from forms.

I think you need to do some more detective work to find out what exactly is
happening and to divorce that form from whatever macro code you have to see
where your problem really is.

 

[alohrer]

I'll keep investigating. The problem is that this form has been
around for about 4 years. We're looking into a more solid option
since when this was built, it was only supposed to be temporary. I'm
saying this 4 years after the fact. So changing it now could prove to
be quite difficult, and if I'm going to change the form itself, I'd
rather invest that time into putting in a true solution.

Just for clarification, we're not sending the actual form. We collect
the information and then we compile a Microsoft Word Document and
another email that contain just the text from the form. The form is
then closed but is never sent. This might not clear too many things
up but again, I'll keep investigating.

 

[Sue Mosher [MVP-Outlook]]

Your original post didn't give your Outlook version or say whether you'd thoroughly investigated the possibility that these are one-off items. The MessageClass and Size property values should tell you for sure.