I created a form using Visual Basic from Outlook.
Now I wish to move it to a public folder that I am the
owner of.
I can run it from my machine. I can export the macro as a
form file. But I can't seem to place it in a public
folder.
Where do I go from here?
I posed the following statement/question to a list of Outlook experts:
"Aside from not knowing what this beast really is, I am about to say
that he can’t put a VB form, even if designed for use in Outlook, in a
public folder, as only custom forms, customized from Outlook standard
forms, can be put in Outlook folders. Is this really true? Or is it
that you just have to make sure that your form has all the parts of the
standard Outlook item? Seems to me that we used to say that you could
make them in C++ and Borland's C++-like rapid-application developer."
The reply I got from Sue Mosher, a respected author of Outlook books,
is:
"Yes, that's true. VB/VBA userforms and Outlook forms are not
interchangeable.
What you could use C++ to make would be Outlook forms, using Extended
MAPI."
So, where you go from here is back to the drawing board. 1) You can
run your form as an Outlook Add-in, and bring it up through a VBA
macro, collect the data, and move it into a standard Outlook item and
save the results in a public folder. 2) You can customize a standard
Outlook form in the Outlook development UI, publish that custom form to
the Exchange Organizational Forms Library, or 3) as Sue says, design an
Outlook form in C++ or the Borland product and publish it to the
Exchange OFL Of course, I have no idea how to do that last step, but,
when you become conversant with MAPI forms, it will all be clear to
you.
I would go with 2), but there are risks with any development strategy,
as you have discovered.
Hollis D. Paul [MVP - Outlook]
(e-mail address removed)
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2195
http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US
Mukilteo, WA USA
