S
Sue
I have a custom form (which was written by someone else -
I am a beginner with this) that works fine in Outlook
2000, but is dying in Outlook 2003. They have customized
the contacts to have a "CompanyId" field. Then they have
a form that when a button is clicked, it reads through a
list of contacts and picks out specific ones. At one
point in the code it assigns a variable. They have the
following code:
set xUsers = cContact.UserProperties
set xX = uUsers.Item("CompanyId")
later in the code they do a Trim(xX) and this is where it
comes up with the error. When I do a debug and hover my
cursor over the value of xX, it say that it = nothing.
This code works when there are not alot of records to go
through. Also, it never dies at the same record, so I
know that it is not a specific contact problem. Could
this have anything to do with cache?? Please help!! Any
suggestions would be greatly appreciated.
I am a beginner with this) that works fine in Outlook
2000, but is dying in Outlook 2003. They have customized
the contacts to have a "CompanyId" field. Then they have
a form that when a button is clicked, it reads through a
list of contacts and picks out specific ones. At one
point in the code it assigns a variable. They have the
following code:
set xUsers = cContact.UserProperties
set xX = uUsers.Item("CompanyId")
later in the code they do a Trim(xX) and this is where it
comes up with the error. When I do a debug and hover my
cursor over the value of xX, it say that it = nothing.
This code works when there are not alot of records to go
through. Also, it never dies at the same record, so I
know that it is not a specific contact problem. Could
this have anything to do with cache?? Please help!! Any
suggestions would be greatly appreciated.