Cannot Open Item - Outlook

[SonomaEnterprises]

I have a custom Outlook form that is based upon the IPM.Post item. This
form (saved in an exchange public folder) works fine for a while, but at
some point (after entering data) the form no longer will open. If you
create a new form in the folder it works fine as do previously saved items
until you enter that magical amount of data and it no longer will open. We
have had the admin look at the settings for the folder and all he could find
is a quota for the folder, which we are not even close to.

Are there other settings that would stop a form from opening when it hit a
certain size limit? I have never seen this behavior on a local pst, so I am
not sure if it is an exchange settings or I just never fill enough data in
on one of the items in the local pst.

The size of the custom form (with no data) is approx 3300 bytes and fully
filled out it is about 6300 bytes; as reported by OutlookSpy looking at the
size property.

Jack

 

[Peter Huang [MSFT]]

Hi

Can you give reproduce sample together with the detailed reproduce steps
for us to do further troubleshooting?
So far based on my research, it is hard to say what is the problem.

Thanks for your efforts.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[SonomaEnterprises]

The form is the IPM.Post.Property Location in this pst file:
www.aaoutlook.com/aa/prop.zip

The steps that cause this to happen is the form is:
Open the Pst file in Outlook
In a contacts public folder select a contact and then create a Property
Location (create-select form from the prop.pst- prop folder)
Incrementally fillout the data on the form and save/close.
The form will save and close fine, until you get to a point (generally it is
after I fill in the Location Info, Expenses and the first two tabs of the
Listing Sales)
Then when you save and close the form it reports that " The Operation cannot
be performed because the message has changed"
Then a copy shows up in local failures

Jack

 

[Peter Huang [MSFT]]

Hi

I think you may try the steps below to see if that works for you.
1. right click the contact folder in "public folders"
2. select properties
3. select "Activities"
4. Click new button
5. select the corresponding contact public folder and click OK
6. then try again


Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[SonomaEnterprises]

Peter,

I tried what you suggested and as I expected it did not make a difference.

The issue that I have does not have anything to do with the activities tab
of the contact record, it is a problem with a custom form not being able to
be saved in a public folder after a certain about of data is stored in the
form. It seems to fail to save when the size is only about 3kb.

I am including the copy from the original posts below for more info.

Original post:
I have a custom Outlook form that is based upon the IPM.Post item. This
form (saved in an exchange public folder) works fine for a while, but at
some point (after entering data) the form no longer will open. If you
create a new form in the folder it works fine as do previously saved items
until you enter that magical amount of data and it no longer will open. We
have had the admin look at the settings for the folder and all he could find
is a quota for the folder, which we are not even close to.

Are there other settings that would stop a form from opening when it hit a
certain size limit? I have never seen this behavior on a local pst, so I am
not sure if it is an exchange settings or I just never fill enough data in
on one of the items in the local pst.

The size of the custom form (with no data) is approx 3300 bytes and fully
filled out it is about 6300 bytes; as reported by OutlookSpy looking at the
size property.

Follow-up Post:
The form is the IPM.Post.Property Location in this pst file:
www.aaoutlook.com/aa/prop.zip

The steps that cause this to happen is the form is:
Open the Pst file in Outlook
In a contacts public folder select a contact and then create a Property
Location (create-select form from the prop.pst- prop folder)
Incrementally fillout the data on the form and save/close.
The form will save and close fine, until you get to a point (generally it is
after I fill in the Location Info, Expenses and the first two tabs of the
Listing Sales)
Then when you save and close the form it reports that " The Operation cannot
be performed because the message has changed"
Then a copy shows up in local failures

 

[Peter Huang [MSFT]]

Hi

So far I think we need to isolate the problem.
First have you tried another form, e.g. a form may be simple or complex to
see if that works.
If all is failed, I wonder if you have permisson to create(save form) in
the public folder.

BTW: this newsgroup is mainly for COM Addin develop support, the problem
seems to be more related with use/configure outlook/exchange, I think you
would better post in the newsgroup below.
microsoft.public.outlook.program_forms
microsoft.public.exchange.admin

There will be more experts on use/configure.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[SonomaEnterprises]

Peter,

I have tried other less complex forms and they seem to work fine. I even
created a custom contact form in the folder with a lot of data (make the
form size much larger than the point where problematic form fails) and it
saved fine.

I also made a copy of this form and put it in a local (pst based) contact
folder and do not see this behavior, I can add all the data I like and it
works fine.

I did post my question in the exchange form, the reason I opted for this
forum is that it is listed as a 'Managed forum' in msdn where the exchange
and the program forms is not and I have posted to those forums before and
only receive a response less that 50% of the time.

Any other ideas would be very much appreciated.

Jack

 

[Peter Huang [MSFT]]

Hi Jack,

So far I am still researching the issue, if I have any new information I
will update you with new information ASAP.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Peter Huang [MSFT]]

Hi

Please check the below articles regarding limitations with custom forms.
There is no exact limit to the number of fields and controls you can use on
a custom Outlook form, but Microsoft Product Support Services recommends
that custom Outlook forms have fewer than 300 controls or user-defined
fields, otherwise the form may not function correctly.

OL2000: Forms Support Limited Number of Fields, Controls
* http://support.microsoft.com/?kbid=229096

OL2000: Custom Forms and Programming Limitations
* http://support.microsoft.com/?kbid=266428

How to use the Outlook 2003 forms cache and to troubleshoot forms cache
problems
* http://support.microsoft.com/kb/839804

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[SonomaEnterprises]

Peter,

Thank-you, that in fact was the issue. The limits on an Exchange server are
clearly different than when running against a stand alone pst; which I was
not aware.

What I did is initialize the majority of the controls to null in the form
definition, this will give me a bit of time to work on changing the form so
that multiple controls will save data in a single field In doing this the
data will be read and parsed on form read and consolidated and saved on form
write.

Thanks for your assistance on this issue!

Jack

 

[Peter Huang [MSFT]]

Hi

You are welcomed!

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.