Datepicker

[JohnG]

Following your previous advice Sue I installed the mscomctl2.ocx, registered
it and installed it to the control box.

I can now put a datepicker control on the compose portion of a message based
form and it appears to work fine.

But when I copy that control and paste it on reply side of the form it
doesn't take the compose form sides input and copy it to the reply side. As
in when they pick a date on the compose I want that exact same date they
picked to be duplicated to the reply side when I answer the form and send it
back.

The reply side acts like a completely new control box w/no relation to the
compose side. I have done the copy and paste for other controls that do mimic
each other just fine except in this case.

I'm using Outlook 2002 on Windows XP Pro if that has anything to do with it.

Any advice appreciated yet again.

John

 

[Sue Mosher [MVP-Outlook]]

"reply side of the form"? You mean the read layout? Did you bind it to the same Outlook field?

A reply is a new item. If the field value isn't being copied, you can always put code in the Item_Reply to copy the value.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[JohnG]

So I should design the form using the seperate read layout, then activate the
read layout and everything should copy over?

 

[JohnG]

Well nevermind for now, I got bigger problems. I just tested the datepicker
by "run this form" and I can pick a new date just fine but when I send it to
the set email address and open it up today's date shown, not the date picked
by the user.

So I need to chew this problem over first anyways.

 

[Hollis Paul [MVP - Outlook]]

But when I copy that control and paste it on reply side of the form it
doesn't take the compose form sides input and copy it to the reply side. As
in when they pick a date on the compose I want that exact same date they
picked to be duplicated to the reply side when I answer the form and send it
back.

The reply side acts like a completely new control box w/no relation to the
compose side. I have done the copy and paste for other controls that do mimic
each other just fine except in this case.

I'm using Outlook 2002 on Windows XP Pro if that has anything to do with it.

Any advice appreciated yet again.

John

That is because it is a completely new control. What you need to do is design
the common elements of the form before you split the form into a compose and
read form. That way, the contents of the control will autoload into the similar
control on the read page.

Go straight to Jail, do not pass go, do not collect 2,000,000 dollars!

 

[Sue Mosher [MVP-Outlook]]

Did you bind the date/time control to an Outlook field?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Hollis Paul [MVP - Outlook]]

So I should design the form using the seperate read layout, then activate the
read layout and everything should copy over?

What on earth do you mean by "So I should design the form using the separate
read layout"? You get a blank form to design. When it opens you can edit
either the compose page or the read page. (This is a really stupid default
setup that Microsoft put into their product. People, who do not need a split
form--that is, who do not really want any differences between the read form and
the compose form--automatically create a compose form and ignore the read form,
and then wonder why nobody can see their form. The form should open as one
unsplit form!) The first thing you should do is drop down the Forms Menu and
uncheck the Separate Read Layout. Now you can compose all the common features
of your form. When that is done, you can click the Separate Read Layout menu
button, and all the controls you have already designed appear on both the
compose and the read layouts. Now you add the unique elements to the compose
and/or read layouts. When done you can publish and test the form.

What you have never questioned is whether you, in fact, need a split form. Do
you really have something on the compose form that you do not want to see on the
read form? Or, vice versus?

 

[JohnG]

Yes I made that mistake exactly Paul. When I created the form it was already
in a seperate read/compose layout. Until you said something I did assume I
had to create both sides myself, but now I understand I don't.

Although I do need a seperate read layout 98% of the form is the same as the
compose I will do as you have instructed thank you.

 

[JohnG]

No I did no bindings at all, I thought the field itself was enough. I'm just
beginning to figure out the logical relationships in the forms and what seems
obvious isn't yet second nature to me. Thanks for the reminder.

 

[Sue Mosher [MVP-Outlook]]

The key concept is that a control on the design surface is not the same thing as a property (i.e. field) in the underlying item.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers