No content in receiver of form

[John Dijkman]

I am pretty sure this is so silly and obvious but this is
my first form and I am obvious doing something silly.

I am trying to make a form with outlook 2000.

The build of it goes fine.
The sending it goes fine.

When it arrives at the other end it does not have the
content of the form that was send? I cannot find anything
in help etc so your help would be really appreciated to
get me going.

Kind regards,

John

 

[Sue Mosher [MVP-Outlook]]

Likely causes:

1) You created a compose layout for the form, but not a matching read
layout.
2) You're sending to someone inside your organization and didn't publish the
form to the Organizational Forms library.
3) You're sending to someout outside your organization and didn't check the
"send form definition with item" box on the form's (Properties) page -or-
don't have the recipient marked for rich text -or- the mail server ate the
rich-text content.

See http://www.outlookcode.com/d/sendform.htm for more information.

 

[John Dijkman]

Sue, you were absoluttely right.
One other question if you do not mind: There must be a way
to protect the form which I do not seem to be able to find.

Your help would be really appreciated.

Kind regards,

John

 

[John Dijkman]

Thanks Sue,

Its the form really, content I already read that this was
not really feasible.

Thanks,

John

 

[Sue Mosher [MVP-Outlook]]

Protect the form design or the data? Neither is 100% protectable, BTW.
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

Neither is the form. You can put a password on it in the (Properties) page,
but I can show you the VBA code to get that password.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Bryan Dickerson]

Please forgive me for butting in again (I know that I do that a lot). I
just found out that I'm having that same problem, for 2 particular users of
a custom form. No one else has complained of this problem using this form.
I was so excited when I saw this thread, but I checked all 3 of the likely
causes and none of them apply. :-( Any other ideas??

 

[Sue Mosher [MVP-Outlook]]

Where is the form published? What format are you sending the mail messages
in? Are both recipient and sender in the same Exchange organization and
using the Exchange service (not POP or IMAP) to connect to the server? What
version of Outlook?

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Bryan Dickerson]

Still not knowing a ton about all the publishing aspects of the forms, I
just assumed that if the form is the default form for a public folder, then
it is published correctly. Is this not the case? The email messages are
taking whatever defaults the user has set up. Generally, emails are edited
with Word as the default editor and in an HTML format. Both recipient and
sender are in the same Exchange organization and both are using the same
method to connect to the Exchange server. The sender is using Outlook XP
and the receiver is on Outlook 2003.

I think we are nearing my knowledge limit about this--and I'm supposed to be
the support for these forms! LOL!

 

[Bryan Dickerson]

I meant to include, if it might help, that I walked the sender thru to the
"Clear Cache" button and when he presses it, he gets this message:

"The Forms Manager dialog box could not be displayed."

 

[Sue Mosher [MVP-Outlook]]

No, that's not correct. The only items that will be able to use that form
will be those stored in that public folder. If you want recipients to be
able to view message from their Inbox with that form, it must be published
to the Organizational Forms library or to each user's Personal Forms
library.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

I'd run Help | Detect and Repair to see if that fixes it.