Re: Should i use ADO to open a text file?

I have to correct what i stated in my previous reply.

The data *is* in the redordset. It's just that the field names are changed
after executing the casInputFileRecordset statement.

However, the data is not populated into the Excel workbook when i execute
this statement:

newExcelWork***.Range("A2").CopyFromRecordset casInputRecordset

This whole program was working before i converted over to the ADO method of
opening the text file. Maybe there is another way to add data to the
workbook because i'm now using an ADO recordset?

Any help would be gratefully appreciated.

Thanks,
Tony

"Ralph" <nt_consulting64@xxxxxxxxx> wrote in message
news:%23GFyOTQYIHA.5160@xxxxxxxxxxxxxxxxxxxxxxx

"Tony Girgenti" <tony(nospam)@lakesideos.com> wrote in message
news:OeKJQdPYIHA.4712@xxxxxxxxxxxxxxxxxxxxxxx
I see. Being a novice at this stuff, I need to reread about that in
Francesco Balena's book. He has a chart showing the relationship between
DAO, RDO, and ADO. There is one block "Jet engine" coming from "DAO 3.5"
and going to "ODBC Driver Manager". Is "Jet engine" the same as
"Microsoft.Jet"?

Also, does the "OLE" in OLEDB" stand for Object Linking and Embedding?

Thanks,
Tony


To find what you need on the web this quick 40,000 foot view might help.

All database access from VB can be done by using a variety of components,
technologies, interfaces, and protocols. These components form a 'stack'.
Programming Lanugage (VB)
Data Access Library (DAO, ADO, OO4O, and RDO)
Data Provider/Driver (OLE DB, ODBC, OCI)
Database Engine (Jet, SQL Server, Oracle)
The Data (MDB, SQL Server, Oracle, ...)
Note: I included MDB (Jet formated flat-files), SQL Server (a RDBMS), and
Oracle (yet another RDBMS) to demonstrate that this applies to ALL
database
access. You can pop in and out various components at either level.

In your case:
Your Code -> Uses an Data Access Library (ADO)
The Data Access Library -> Uses a Provider (OLE DB)
The Provider/Driver -> Uses a Database engine (Jet)
The Jet engine -> Uses the MDB data store (a Jet formatted file)

OLE does have roots with an early inter-process technology termed "Object
Linking and Embedding". Over time with enhancements this evolved into an
advanced IP technology with its own specification called just "OLE" (or
OLE
2). It is associated with COM. COM is a distributed object specification.
OLE is Microsoft's implementation of COM. (But it isn't 'COM' - its the
machinery behind COM.)

"Jet" refers to the proprietary Microsoft Jet Database Engine. It is also
often used to refer to "Jet Formatted" database files.

When reading about any of these technologies it is important to note the
context within which the term is used - all of them can be seen from
various
points of view - conceptually from its interface to something else, its
specification, rules, or methods, or as its implementation or how it works
internally. But don't try to understand everything at the beginning. Many
a
programmer has done quite well working with ADO without a clue of what the
engine or provider is actually doing. That's the beauty of all these
technologies - they abstract the whole process down to a simple interface.

hth




.