Will readily agree with Ken - vast majority of cases will likely be handled
with a text(255) field. If you're writing for a single location and aren't
running over the 255 char limit with anything now - you're probably safe
with that size as were all the Exch sites using our programs at the outset.
Since the issue got dealt with as soon as the problem was located, have no
idea how prevasive the issue of > 255 characters is or under what
circumstances - never looked back to find out. It took several months for
the problem to surface originally and in both reported incidents involved
new customers who coincidently installed/eval'd within days of each other.
So yes, if you never want to worry about field size for EntryID under any
circumstances - memo field would be the choice.
Karl
_____________
ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter
"Power contact importers/exporters for MS Outlook '2000/2007"
"DPM" <aa@bb.cc> wrote in message
news:%23GDx$ZtzJHA.3988@TK2MSFTNGP05.phx.gbl...
> Thanks Karl.
> So it's ideal to use a Memo field.
> "Karl Timmermans" <karl@claxton.com> wrote in message
> news:ub103TlzJHA.1420@TK2MSFTNGP04.phx.gbl...
> > Discovered the hard way many years ago that the Exch EntryID can exceed
> > the
> > max Text length of 255 for an Access DB using Contact.EntryID's (assuming
> > the same applies to MailItem). While this may simply be a coincidence,
> > the
> > issue only surfaced for 2 European installations (European Exch beta
> > sites
> > worked just fine and and never was an issue for North American Exch
> > configs.
> > Issue was fixed very early so no way to know if geography was at
> > all significant). Problem solved by changing to a Memo field.
>
>> Karl
> > _____________
> >
> > ContactGenie - Importer 1.3 / DataPorter 2.0 / Exporter
> > "Power contact importers/exporters for MS Outlook '2000/2007"
> >
>
>
>
>
>> "DPM" <aa@bb.cc> wrote in message
> > news:%23U3knWjzJHA.3404@TK2MSFTNGP02.phx.gbl...
> >> Hi,
> >
>>> I am using a DB to store the EntryIDs of MS Outlook emails, so that
> >> these
> >> mails can be referred later using the DB.
> >
>>> What I noticed is the length of the MSO MailItem.EntryID is,
> >> - 48 characters for normal MSO 2003 SP2
> >> - 140 characters for MSO using exchange server
> >
>>> Could someone please advice what is the maximum length, a MSO
> >> MailItem.EntryID could have with any other configuration, to decide on
> >> the
> >> length of the DB field?
> >> or
> >> Is there any other fixed length MailItem attribute which could be used
> >> to
> >> uniquely identify a mail item in MSO?
> >
>>>
>
>
>>
>