general Q and specific Q re. ADODB

[Dick Watson]

I'm trying to replace something that was done with linked .CSV tables, link
specification, and VBA. I want to do the whole process (parsing some .CSV
with poor/inconsistent data typing and blank lines and other bad things that
break straight queries) via VBA and ADODB using the Microsoft.Jet.OLEDB.4.0
provider.

General Q: can someone point me to a one-stop source of reference-level
documentation on ADODB as accessed by the Microsoft.Jet.OLEDB.4.0 provider?
I've found lots of stuff on google on little portions of this and lots of
specific examples, but, for instance, can't seem to find a complete source
for what can be specified in the connection string for the
Microsoft.Jet.OLEDB.4.0 provider.

Specific Q: how do I replace the link specification that I can define from
the Access UI with code and/or schema.ini and/or ???

Thanks in advance for any assistance!

 

[Dick Watson]

The answer to that appears to be the right link in MSDN (MSDN \ MSDN Library
\ Win32 and COM Development \ Data Access and Storage \ Windows Data Access
Components SDK \ Microsoft ActiveX Data Objects (ADO)) and, apparently, the
MDAC SDK. But I'm still not finding documentation for things shown in the
examples I'm seeing out on the web. Nor have I found the answer to my
specific question.

 

[david]

Specific Q: how do I replace the link specification that I can define from

the Access UI with code and/or schema.ini and/or ???

Originally, you could look at the VBA code in the library, and
modify and copy it as you wish. Now you can't: it's a black box.

But that process (including schema.ini) only works for well structured
data anyway. You want generic CSV code instead. Here is one
example: there are many others

http://www.rogersaccesslibrary.com/forum/forum_posts.asp?TID=361

(david)

 

[Dick Watson]

Thanks for the link. With these and other examples and a lot of persistence
I think I'm getting where I want to go. Even the "definitive" documentation
that is scattered about MSDN--some of which only google will find--shows
just a subset of the functionality you can find scattered about in examples
on the web.