Re: Problem getting Outlook custom form to print to Word

It works!
It was the lack of the message body that was causing the error. And when
this is published there should be no problems at all.

Sue, again, thank you for taking the time to lead a newbie by the hand and
point what should be obvious. Enjoy your day/night!

Duane

"Sue Mosher [MVP-Outlook]" wrote:

The object browser (F2 in VBA) is your friend. A MailItem has no Message property but it does have a Body. Adding it back to your design will also give recipients access to any attachments, which otherwise will be inaccessible.

I don't know if that will fix the error your seeing, though. It's not one that I know how to reproduce, although there are MSKB articles on similar errors.

Sorry about leaving the s off FormFIelds.

The forms I have created, one gentleman at the company, when he opens the
Outlook template from his computer, all he sees is a normal email, not the
form.

What exactly is he opening? A saved .oft file? An item created with a published form? Everyone who needs to use the form needs access to the published form definition, and items need to be created with the published form, not an .oft file. ALso, the form should be published with the "send form definition with item" box on the (Properties) page unchecked.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"Duane Nutley" <DuaneNutley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:8914FCA1-5C76-4DAD-8903-784065758FF2@xxxxxxxxxxxxxxxx
Sue,
The check boxes work! Of course only after making it oDoc.FormFields, not
FormField. So that one is now off the list.

The error when attempting to open the form once it has been received is as
follows:

"Can't open this item. Could not complete the operation. One or more
parameter values are not valid".

I am wondering if this is because I deleted the message body field. I could
not find the VBA code to get information from an email body (I thought it was
Item.Message), so I deleted the message body field and inserted a text field.

Something slightly related to this - Why is it that some people cannot view
an Outlook form correctly? Instead it comes up as a normal email message.
The forms I have created, one gentleman at the company, when he opens the
Outlook template from his computer, all he sees is a normal email, not the
form.

Duane


"Sue Mosher [MVP-Outlook]" wrote:

Regarding the checkbox, the correct syntax would be:

oDoc.FormField("Check1").CheckBox.Value = Item.UserProperties('your yes/no field")

The appearance in the reading pane is perfectly normal for a custom form that has code behind it. The error message could be due to code in the Item_Open event hander, which doesn't run until the user opens the item. The exact text of the error message would probably be helpful.


"Duane Nutley" <DuaneNutley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:69A1FF20-15C3-4FFF-8DE1-8D3B2560AE46@xxxxxxxxxxxxxxxx

However I have now noticed that 3 checkboxes on the Outlook form are not
filling in their equivalent Word tickboxes. I had a look at some other posts
about checkboxes and I am not sure what is causing the fault.

The field is called something like Fee Acknowledged and is a Yes/No Field.
When I rightclick on the control on the form, in the Value tab, it says it is
looking for the field Fee Acknowledge, is a Yes/No field and will display the
Icon. Is there anything else I need to change to get it to work?

Also I used the suggestion of oDoc.FormField("Check1") = user.itemproperties
code (sorry I cant remember the actual code that was used, but it was
different to what I used) and an Error about Value Mismatch came up. Now I
dont understand why that would occur as it has been told to look for a Word
form field called Check1, that is a tickbox, and on the Outlook form it is a
Yes/No field.

My last problem (and a new one I have never seen before), I can create the
form, have it print out (minus the tickboxes being selected) and send it to
someone all fine. But in Outlook Inbox, in the preview pane it says it needs
to be opened to view the contents (which I understand and am ok with). BUT
when I double click to open the email, an error message occurs, stating that
a value parameter is not valid and it will not open the email.
I have never seen this problem before and wonder if you know what might be
causing it? It has only come up so far when I tested the form by using the
Run this Form command under Form menu, while in the Design mode of the
Outlook form.



.

Relevant Pages

  • Re: Problem getting Outlook custom form to print to Word
    ... Adding it back to your design will also give recipients access to any attachments, ... Sue Mosher, Outlook MVP ... Instead it comes up as a normal email message. ... The forms I have created, one gentleman at the company, when he opens the ...
    (microsoft.public.outlook.program_forms)
  • Re: Problem getting Outlook custom form to print to Word
    ... Author of Microsoft Outlook 2007 Programming: ... I am wondering if this is because I deleted the message body field. ... Instead it comes up as a normal email message. ... The forms I have created, one gentleman at the company, when he opens the ...
    (microsoft.public.outlook.program_forms)
  • Re: Phone Message - Custom
    ... anyone can insert the name from Outlook or Exchange. ... Wouldn't the coding be: ... into the message body, ...
    (microsoft.public.outlook.program_forms)
  • Re: Phone Message - Custom
    ... Sue Mosher, Outlook MVP ... I'm just going to be using the Caller, Companytext and Phonetext. ... Yes, if Caller, Companytext, and Phonetext are the names of custom fields and you also have a statement to set the message body to the string you're building: ... So how can you enter that into your vbscript? ...
    (microsoft.public.outlook.program_forms)
  • Re: Phone Message - Custom
    ... Sue Mosher, Outlook MVP ... I'm just going to be using the Caller, Companytext and Phonetext. ... Yes, if Caller, Companytext, and Phonetext are the names of custom fields and you also have a statement to set the message body to the string you're building: ... So how can you enter that into your vbscript? ...
    (microsoft.public.outlook.program_forms)