[aus-dotnet] inconsistent results using getoledbschematable

[askoop@xxxxxxxxxxxxxxxx]

oletable =
oledb.getoledbschematable(system.data.oledb.oledbschemaguid.tables
,new object() {Nothing,Nothing,Nothing,"TABLE")

the above command will generate an ado.net datatable
containing all the user tables in the connected database.

I'm getting inconsistent results however depending on which
(mdb) file I am opening via an oledbconnection.

It either works perfectly or I get the message:-

Object reference not set to an instance of an object

Since it works on some files and not others, is this a case
of ado.net not being robust in all instances. If so I'm
using vs 2003, does anyone know if ADO.NET is more robust in
vs 2005, or are there some anomolies in the line of code I'm
using.

Steve.
---
[This E-mail scanned for viruses by Declude]

_________________
You are a part of the Australian "dotnet" mailing list.
To unsubscribe send "unsubscribe dotnet" or to re-subscribe send "subscribe dotnet Your Name" in the body of the email to: imailsrv@xxxxxxxxxxx
List managed by: http://www.stanski.com