Problem with customized outlook forms

M

Muhammad Usman

Hi Community,

I am suffering from a very strange problem. I have developed a customized
form. This customized form has been published in Organization form library.
When i create a new contact item while using that customized form, it works
fine. Form opens as it required to be. The Item_Open event written in vb
script in code section works well. New item is created. All is good. But when
i open this saved item, the Item_Open event is not called and hence all the
functions that are called in Item_Open event are not called. I am unable to
know that why this strange behaviour is occuring.
I need very quick response over it due to strict timelines

Thanking you
 
M

Muhammad Usman

Thx Paul
The purposed solution mentioned in the article is that "Do not use possible
values" property of the combo box to avoid from to be one-off ed form. Use
list property or ListItem to add items in the combo boxes. i am using List
property to bind my array of data to the contro. So this problem should not
come. The problem arises when i open the saved item. When i open the saved
item, the Item_Open event does not fire.
Is there any possibility that when i click on "Save and Close" button, the
form becomes one-off. Just a thought. Don't know what's the theory behind
this problem.

Regards
 
M

Muhammad Usman

Thanx Paul

You very intelligently thought about the problem. Infact form was becoming
onf-off when i was saving it. It's message class was being changed that made
it happen to be one-off.

Thanx Paul once again

Best Regards
 
S

Sue Mosher [MVP-Outlook]

There are many other possible code statements or scenarios that can one-off an item. See http://www.outlookcode.com/d/secforms.htm

The MessageClass and Size properties of the saved items will clearly tell you if they're one-offs.

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

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

Hollis Paul [MVP - Outlook]

You very intelligently thought about the problem. Infact form was becoming
onf-off when i was saving it. It's message class was being changed that made
it happen to be one-off.
Unfortunately, that does not pinpoint the problem. The only solution is to go
back to the last-good version of the form and re-design it. This time, make
very small changes (like 1 control at a time) and republish and test. Make
sure that you keep at least three generations of the published form so you
aren't forced back to ground zero when the one-off condition finally occurs.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top