>>What is ADO to me? Take a shotgun and blow a hole in VFP's head and you
have >ADO. Actually, ADO is a great idea if you spend your days accessing
data in >spreadsheets and text files etc. I prefer to use a database. I use
VFP with >SQL Server. ADO does that too. It uses ODBC. VFP also uses ODBC.
So now if we >could just get VFP to use ADO (so it could do the ODBC
instead of VFP doing it >directly) we would get to:
>
>ADO uses an OLE-DB provider for ODBC. This was necessary for the huge
installed base of ODBC. Except for one thing, ADO does not have the
over-head of the ODBC connection manager. Yes, ADO makes use of the ODBC
Driver for a particular DB - if you use the ODBC OLE-DB provider. There are
specfic OLE-DB provider for Jet (JOLT), SQL-Server, etc. These providers
are not ODBC.
(I've been skipping the VFP bashing & VB is better threads but this thread
has not been that way ... until now.)
Personally, I found it great, after years of having to
setup DSN connections on every damn machine, to use
DSNless connections through ADO.
No more ODBC & DSNs.
Just link straight to the database.
YEAH!!!
Long live ADO.
.Signature
{
margin-top: 12px;
color: #666666;
}
.Signature a
{
color: #666666;
}
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only