dissappearing fields

A

amit naik

I have created a custom form based upon a post item. I
have then published it to an exchange public folder. The
form is working fine, however, certain fields are set to
invisible by default and later the property is changed by
code depending on certain conditions. If you then sae the
form, when you re-open the form, the fields return to
bieng invisible again. I have not written any code to do
this, does anyone know why it would be happening?
 
S

Sue Mosher [MVP]

What does the code do? Runtime changes to the UI are not persistent. If you want the form to appear in the same state the next time someone opens it, you must save state information to Outlook properties when the item closes and apply that information in your Item_Open event handler.
--
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
 
G

Guest

Basically, im not sure if I have chosen the right route
but here is a breakdown of what I want to do. I need to
model a workflow process. When a new workflow is started,
one task appears on the post based form(as well as other
information). When that task is complete, another task
shows up on screen and so forth. Tasks are simply a
series of textboes with the task name appearing in them
and deadline info and so forth. But when somehas
completed a task, an email is sent to the person
responsible for the next task, however when they open the
form, which is in a public folder, the task remains
invisible again!!!!

What code do I need to use to save state information and
retrieve it?
-----Original Message-----
What does the code do? Runtime changes to the UI are not
persistent. If you want the form to appear in the same
state the next time someone opens it, you must save state
information to Outlook properties when the item closes and
apply that information in your Item_Open event handler.
 
S

Sue Mosher [MVP]

You set a value in one or more Outlook properties -- built-in or custom -- that reflect the information you need to restore the state. Do that in the Item_Close or Item_Write event handler, then reverse the process in the Item_Open event handler: Read the state information, then do whatever you need to the controls.

In other words, you have to save whatever information will let Outlook know what controls to show. The exact details depend entirely on your application.
--
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
 
G

Guest

thanks for your help Sue, your help is much appreciated
-----Original Message-----
You set a value in one or more Outlook properties --
built-in or custom -- that reflect the information you
need to restore the state. Do that in the Item_Close or
Item_Write event handler, then reverse the process in the
Item_Open event handler: Read the state information, then
do whatever you need to the controls.
In other words, you have to save whatever information
will let Outlook know what controls to show. The exact
details depend entirely on your application.
 

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