I'm working in Access 2003 with a Redemption MAPITable object to obtain a
subset of Exchange's GAL (Address Book). In the following code that I have
written for test purposes, whenever the retrieved field (e.g. 'PR_INITIALS')
is empty, the expression Row(x) contains a binary error code that I cannot
deal with. Any Ideas as to what to put in the function HandleEmpty, so that
HandleEmpty(Row(x)) returns a string?

......code snippet.....................
...
Rows = Table.GetRows(CHUNKSIZE)
If Not IsEmpty(Rows) Then
For i = LBound(Rows) To UBound(Rows)
Row = Rows(i)
Debug.Print (HandleEmpty(Row(0)) & vbTab &
HandleEmpty(Row(1)) & vbTab & HandleEmpty(Row(2)) & vbTab &
HandleEmpty(Row(3)) & vbTab & HandleEmpty(Row(4)))

Can you use the IsEmpty function on the row first and then on each column as
you read it? That's what I do.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"SummerSky" wrote in message
...
I'm working in Access 2003 with a Redemption MAPITable object to obtain a
subset of Exchange's GAL (Address Book). In the following code that I have
written for test purposes, whenever the retrieved field (e.g.
'PR_INITIALS')
is empty, the expression Row(x) contains a binary error code that I cannot
deal with. Any Ideas as to what to put in the function HandleEmpty, so
that
HandleEmpty(Row(x)) returns a string?

.....code snippet.....................
...
Rows = Table.GetRows(CHUNKSIZE)
If Not IsEmpty(Rows) Then
For i = LBound(Rows) To UBound(Rows)
Row = Rows(i)
Debug.Print (HandleEmpty(Row(0)) & vbTab &
HandleEmpty(Row(1)) & vbTab & HandleEmpty(Row(2)) & vbTab &
HandleEmpty(Row(3)) & vbTab & HandleEmpty(Row(4)))

I tried that. In my case, the function IsEmpty, when fed an error-inducing
Row(x) argument, returns false, because the Row(x) contains the infamous
MAPI_E_NOT_FOUND array of variants error, and thus is not an appropriate
discriminator.
I solved the issue the ugly but effective way by assigning every Row(x) to a
string variable. The type mismatch error that then occurs when a
MAPI_E_NOT_FOUND is assigned to the string variables, is ignored by the
subroutine by a nice "on error resume next" statement.

"Ken Slovak - [MVP - Outlook]" wrote:

Can you use the IsEmpty function on the row first and then on each column as
you read it? That's what I do.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"SummerSky" wrote in message
...
I'm working in Access 2003 with a Redemption MAPITable object to obtain a
subset of Exchange's GAL (Address Book). In the following code that I have
written for test purposes, whenever the retrieved field (e.g.
'PR_INITIALS')
is empty, the expression Row(x) contains a binary error code that I cannot
deal with. Any Ideas as to what to put in the function HandleEmpty, so
that
HandleEmpty(Row(x)) returns a string?

.....code snippet.....................
...
Rows = Table.GetRows(CHUNKSIZE)
If Not IsEmpty(Rows) Then
For i = LBound(Rows) To UBound(Rows)
Row = Rows(i)
Debug.Print (HandleEmpty(Row(0)) & vbTab &
HandleEmpty(Row(1)) & vbTab & HandleEmpty(Row(2)) & vbTab &
HandleEmpty(Row(3)) & vbTab & HandleEmpty(Row(4)))