Error opening recordset where table is empty (but has field names) - How do I avoid?

[Alan]

Hi All,

This is a supplementary question to my other plea for assistance:

http://groups.google.co.nz/group/mi...52a8f/1ddb175249696512?hl=en#1ddb175249696512

OR

http://tinyurl.com/a9vhr



As a workaround for that issue, I have created an MDB file with linked
tables to the FoxPro DB.

I am then pulling the data from access into excel using
ADODB.Recordset objects.

My code works fine (albeit extremely slowly) but falls over on this
line:

rs.Open TableList(Count), cn, adOpenKeyset, _
adLockOptimistic, adCmdTable

for the table that has field names but not actual records.

I have tried surrounding that line with an error trap thus:

On Error GoTo NextTable

rs.Open TableList(Count), cn, adOpenKeyset, _
adLockOptimistic, adCmdTable

On Error GoTo 0

However, it still stops there with an ODBC error.

Is there any way to check for an empty table that won't generate an
error and cause the code to abort?


Thanks,

Alan.

--
The views expressed are my own, and not those of my employer or anyone
else associated with me.

My current valid email address is:

(e-mail address removed)

This is valid as is. It is not munged, or altered at all.

It will be valid for AT LEAST one month from the date of this post.

If you are trying to contact me after that time,
it MAY still be valid, but may also have been
deactivated due to spam. If so, and you want
to contact me by email, try searching for a
more recent post by me to find my current
email address

 

[Patrick Molloy]

how about checking first with
SELECT COUNT(8) FROM TABLENAME
?
If this returns 0 then skip the enext bit.

Or set the recordset to read the data then check it recordcount property