Stephen the Cook wrote:
Leland Jackson <> wrote:
What are the advantages of using OLE-DB other than windows lock in?
LOL. Everyone except Microsoft still standardize on ODBC. OLE-DB is
slower than ODBC, and can require rewriting of applications should
you decide to move to the Window world. OLE-DB uses a first, next,
previous, last method to walk through record sets, which is not well
suited to web based application that do not have local network
speeds; although, it fine for desktop application.
All the major vendors, except Microsoft, provide their own ODBC
drivers for windows, and most now also provide OLE-DB as well as a
connection layer that can be used by .NET. So far as I can see,
there was no valid reason for Microsoft to go to a new
non-standardized OLE-DB provider, other than Microsoft desire to try
and monopolize the database server market to go along with its
monopoly of the windows desktop market. In the Microsoft world,
there is only one database name MS SQL and only one OS named Windows.
Outside of them, nothing else exits. <g>
AutoInc in a dbc just as a start. Oh how about dbc triggers or long names
for fields.
Do you have a window 0S tunnel vision impairment? I was talking about
a OLE/DB connection to VFP compared to using Oracle's, MySQL's,
PostgreSQL's, Informix's or DB2's ODBC provider under windows. So far
as VFP is concerned, it was originally developed to connect directly to
the DBC over a NETBIOS local network, which still works just fine for RI
and auto-increment all the way through VFP9.
VFP was never designed to operate over the Internet's TCP/IP potocol
with remote users connecting to the DBC. VFP was designed to work
within a NETBIOS local network; although, remote user can connect to a
VFP DBC using NETBIOS, this kind of a permanent remote connection to the
DBC and tables, trying to maintain state, does not give satisfactory
performance or reliability over the Internet, compared to the stateless
environments of the big guns that are built specifically to use TCP/IP
over the Internet.
There are some third parties like Openlink that provide OLE/DB and ODBC
drivers for VFP, which do provide a kind of stateless connection to VFP
with a lot of the feature and feel of a database server like MySQL,
PostgreSQL, MSSQL, Oracle, etc, but why would anyone want to use VFP
with one of these expensive drivers, when so many outstanding databases
already have all the problems worked out and provide their own perfectly
good ODBC drivers for anyone who would want to run these databases on a
window OS. Also, both MySQL, PostgreSQL, and many other open source
databases are free, or almost free, which is another plus for them.
Regards,
LelandJ
Stephen Russell
DBA / Operations Developer
Memphis TN 38115
901.246-0159
http://spaces.msn.com/members/srussell/
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
