form size restrictions???

  • Thread starter Thread starter dale
  • Start date Start date
D

dale

Wiath a custom form is there any type of size
restrictions? I have a custom form with many custom
fields. When trying to save I receive this error:
"The item could not be saved to this folder. The folder
has been deleted or moved, or you do not have
permission. Do you want to save a copy of it in the
default folder for the item?" Upon removing some of the
fields and their associated controls the form saves with
no problems. However, I do need the fields & controls
that have been deleted to be able to save it.
Any suggestions??

Thanks.

Dale
 
Yes, there are definite size limits and they're documented in the KB, but a bit vague. Hard limit is 32kb for all data except the message body and attachments. General rule of thumb is that 200 fields is pushing the limit. How many do you have? Sounds like too many. :(
 
Would this also be in your book somewhere??

-----Original Message-----
Yes, there are definite size limits and they're
Click to expand...
documented in the KB, but a bit vague. Hard limit is 32kb
for all data except the message body and attachments.
General rule of thumb is that 200 fields is pushing the
limit. How many do you have? Sounds like too many. :(
 
No, I don't think there's anything in the book on that, though it would be a good thing to mention if we do a revision. It's rather a moving target with no hard and fast limit.

You didn't say how many fields you have.
 
Current the number of fields is 335. Needing to add
about another 50 but could get by with doing these fields
during the print phase (using template in Word). That
includes all text boxes, msg boxes, check boxes and email
fields (send to, cc and subject). I agree this form has
gotten to be complicated and we should look into another
means of performing this function other than outlook
since it has grown.
-----Original Message-----
No, I don't think there's anything in the book on that,
Click to expand...
though it would be a good thing to mention if we do a
revision. It's rather a moving target with no hard and
fast limit.
 
Note however that the code will fail on other machines because &H8239001E is
specific to the particular message store that you are using.
To retrieve the proptag of a named property, you need to call
GetIDsFromNames first passing the appropriate GUID and id (look at the
message using OutlookSpy (click IMessage), select that named property -
OutlookSpy will show the GUID and id in the "Named Property" box), "or" the
returned tag with the appropriate type (e.g. PT_STRING8), and only then use
it to call HrGetOneProp.
See http://www.dimastr.com/redemption/objects.htm#examples for examples.

Dmitry Streblechenko (MVP)
http://www.dimastr.com/
OutlookSpy - Outlook, CDO
and MAPI Developer Tool


John Riddle said:
I'd be really curious to know more about the size limit. Microsoft says
Click to expand...
that the limit is around 32k for all controls, however we have one field (a
resume field that holds job seekers' resumes) that text is pasted into and
can get quite large (sometimes 1 mb or more). Outlook would save just fine
(we have probably 100 custom fields in addition that don't hold a lot of
data). However, if another item was selected and then the original (large
item) were re-opened, the form would open fine, but the resume text field
would be blank. I was working around this by copying the text into an
attachent, saving the item that way and then re-copying the info from the
attachment back to the resume field when re-opening the item.
Well, as you can imagine, it worked, but made every item in the folder
Click to expand...
roughly twice the size as it would have been if Outlook could just read more
than 32k of data in the first place.
This weekend, I used Dmitry's Redemption to read the info directly when
Click to expand...
opening the item and now everything works perfectly. I wrote a script to go
through and delete all the attachments to all contact items in the folder
(more than 15,000) and got rid of a lot of wasted space.
 
Dmitry,

Yeah, I saw a post where Ken was telling someone that was the reason why their code wouldn't work on any other machine but his test machine. The environment we work in is strictly public folder items and we're all on the same exchange server so I didn't go to the extra work. I'll rewrite once I get more practice with Redemption. The purpose of posting it here was to simply show that your tool could retrieve larger text than 32k.

John
 
Back
Top