RE: To help prevent .. objects were not loaded

Hi Sue,
Thanks very much for your patience.
This indeed allowed me to publish the form after which, use of the published
form succeeded.
I have forwarded this procedure to my colleague who is testing for the
customer.

But I have one more question, if I may.
By default, so I read, scripting is enabled for forms in public folders but
not in forms for shared folders.
In order to avoid asking each user to find the check box and enable
scripting, I would like to publish to a public folder.
Is this the correct approach?
Who has permissions to publish to a public folder? Anyone?
If this is not the right approach, can you recommend a procedure that would
save us the logistical nightmare of checking the check box on every desktop
in the organization?

Thanks !

David

"Sue Mosher [MVP-Outlook]" wrote:

In the Tools | Forms | Design Form dialog, you need to choose User Templates
in File System.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx



"David Sackstein" wrote:

Hi Sue,
When I open Tools | Forms I have two options:
Choose Form or Design Form.
Both open the same dialog that doesnt give me access to the filesystem (I am
using Outlook 2003, I understand on 2007 it does allow access).

"Sue Mosher [MVP-Outlook]" wrote:

Yes, an .oft file is a one-off and not suitable for production use. To
publish it, open it with the Tools | Forms | Design This Form command
instead.

"David Sackstein" wrote:

During the course of my development I removed the published forms from my
Personal Folder.
However I do have a copy that I saved as an .otf file.
So this is a one-off. Right?
In order to Publish it to my designated folder I understand that I need to
open it and select Publish To on the Tools / Forms menu.
Well, I never get there, because after double-clicking on the form I am
informed that the code was not loaded. Indeed the Microsoft Spread*** 11.0
control I placed on a tab is also gone.
I would imagine that publishing the form wont make them reappear.
Right?
So what did I miss?

Thanks a lot

David

"Sue Mosher [MVP-Outlook]" wrote:

That warning message is not related to those settings, but is more likely to
be related to a one-off form being in use. See
http://outlookcode.com/article.aspx?id=67

"David Sackstein" wrote:

I created a custom form with some VBScript behind.
Sometimes I get the message above. (Outlook 2007 and 2003)
I enabled the "Allow script in shared folders" and "Allow script in public
folders".
I made sure that in the registry:
under HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Security\ both
PublicFolderScript and SharedFolderScript are enabled.
(by the way I noticed the GUI and the registry keys dont always agree).

Anyway the problem is eratic. I cannot yet determine what exactly caused it
to appear and what made it disappear.
This is very frustrating because I need to deliver it to a customer.

.

Loading