Re: Data access layer for SQL Server & MS Access

Robin;

can it; MP is always right

Just use ADO; that's my vote.

ADO.net is _CRAP_

-Aaron


RobinS wrote:
We both know that's not true. You are the one who is flaming people,
as anyone can tell by your history. You could at least maintain
a modicum of class and not tell lies about other people.

Robin S.
-----------------
"Master Programmer" <master_programmer@xxxxxxxxxx> wrote in message
news:1165563227.558862.152350@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Dont listen to this guy, he just posts messages around these groups
trying to cause trouble and give people the wrong information.

You need to create a custom "Data Access Class" that obscures the type
of database that you are connecting to. OLEDB is way too slow (100
times slower than a native SQL Server connection).

To be honest with the limitations of the .net data tools (IE: no
generic dataReader etc) - you are probably better to keep life simple.
I don't mean to be blasphemous but just import ADO (COM) and use that -
at least it has MoveNext.

The Grand Master
"Visual Basic 6.0 Jihad"


sanders_mike_newsgroups@xxxxxxxxx wrote:
Hi

I have a web app that needs to be able to use either SQL Server or MS
Access - depending upon the installation. I want to avoid having
unnessesary amounts of code (eg: dim x as sqlDataReader, dim y as
OLEDBDatareader in lots of parts of the app)

Could I not just avoid this and use OLEDB for both database types?

Whats the best way - OLEDB or to create some kind of data access layer
that returns recordsets.

Thanks
Mike


.

Relevant Pages

  • Re: Data access layer for SQL Server & MS Access
    ... RobinS wrote: ... a modicum of class and not tell lies about other people. ... You need to create a custom "Data Access Class" that obscures the type ... Could I not just avoid this and use OLEDB for both database types? ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Delphi Community missing the .NET-boat
    ... ODBC, RDO, DAO, ADO, OLEDB, now ADO.NET - All New! ... > group that needs to reinvent data access every goddamn year? ...
    (borland.public.delphi.non-technical)
  • Re: opening ole db databases in access
    ... OLEDB providers via ADO or ADO.NET. ... > doesn't natively support OLE DB providers when this is the ... >> me to use a real e-mail address in public newsgroups. ...
    (microsoft.public.access.externaldata)
  • Re: Need some advice on ADO .NET
    ... William (Bill) Vaughn ... .NET and am coming from a different background (PowerBuilder)? ... As the other folks have said, ADO.NET is an ... >> data access to a variety of backend data access servers and ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: OleDbLiteral
    ... anything in those classes which allows one to access OLEDB ActiveX ... > You can retrieve schema information about any number of database objects, ... RDBMS itself. ... is that ADO .NET dropped the ability to generically get RDBMS specific ...
    (microsoft.public.dotnet.framework.adonet)