Custom Form does not open contacts in drafts folder

[gina.ledesma]

A custom form developed in Windows NT, Microsoft Outlook
97 does not behave the same in Windows XP, Microsoft
Outlook 2002. When the custom form is filled in and sent
to the drafts folder, I can no longer open the contacts
folder using set objAllContacts =
objcontactfolder.items. It currently behaves correctly
in the NT environment, but not in XP Outlook 2002, any
suggestions?

 

[Hollis D. Paul]

It currently behaves correctly
in the NT environment, but not in XP Outlook 2002, any
suggestions?

The Outlook Object Model changes with each new version of Outlook. You
have to go in and find the new name for the object you want to use to
do the function that you want to perform. One should not expect
forward compatibility. One would like to have backward compatibility,
but alas, alack, that has never been the case with Outlook.

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

 

[Sue Mosher [MVP]]

This is a message form? Where is the form published? What is the state of the "send form definition with item" box? Is that a code statement from the form?
--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers

 

[Guest]

thank you for your response.

This is a message form that is published in the personal
forms library, and when published I selected for the
definition to be saved with the item.

In futher troubleshooting the form, the form script
debugger is no longer available once the form is saved
and sent to the Outlook drafts folder. The vb script no
longer runs.

-----Original Message-----
This is a message form? Where is the form published?

What is the state of the "send form definition with item"
box? Is that a code statement from the form?

 

[Guest]

If I understand you correctly, I need to fine the correct
method for this version of Outlook to get the contacts
folder?

I thought I compared the code out on the knowledge base
and it appeared that the code was correct, I'll have to
verify again.

-----Original Message-----

It currently behaves correctly
in the NT environment, but not in XP Outlook 2002, any
suggestions?

The Outlook Object Model changes with each new version of Outlook. You
have to go in and find the new name for the object you want to use to
do the function that you want to perform. One should not expect
forward compatibility. One would like to have backward compatibility,
but alas, alack, that has never been the case with Outlook.

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


.

 

[Guest]

The form works correctly when sending a new message, but
when the message is saved in the Outlook drafts folder, I
try to edit the message using the custom outlook form,
the script no longer runs. The script does not seem to be
available from the drafts folder - I cannot even use
debug.

Gina

-----Original Message-----
This is a message form? Where is the form published?

What is the state of the "send form definition with item"
box? Is that a code statement from the form?

 

[Guest]

Thank you for your response, but I believe I have found
the problem. For some reason, the published form became
a one-off. I have no idea how the setting changed, but
it seems to have solved the problem.

Thank you very much for your help.

-----Original Message-----
This is a message form? Where is the form published?

What is the state of the "send form definition with item"
box? Is that a code statement from the form?

 

[Guest]

Thank you for your response, but I believe I have found
the problem. For some reason, the published form became
a one-off. I have no idea how the setting changed, but
it seems to have solved the problem.

Thank you very much for your help.

-----Original Message-----

It currently behaves correctly
in the NT environment, but not in XP Outlook 2002, any
suggestions?

The Outlook Object Model changes with each new version of Outlook. You
have to go in and find the new name for the object you want to use to
do the function that you want to perform. One should not expect
forward compatibility. One would like to have backward compatibility,
but alas, alack, that has never been the case with Outlook.

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


.

 

[Sue Mosher [MVP]]

Correct. Code does not run on unpublished forms. See http://www.slipstick.com/outlook/esecup.htm#formsec
--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers

 

[Hollis D. Paul]

Thank you for your response, but I believe I have found
the problem. For some reason, the published form became
a one-off. I have no idea how the setting changed, but
it seems to have solved the problem.

A form becomes one-offed because there is something in the code that
changes the form definition so that it no longer matches the original.
Are you deleting controls or adding them in runtime?

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