Re: rs.RecordCount issue...

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Irfan wrote:
sorry guys, i'm new to all this, i actually did use OLEDB and now i
realize i have mix of ADO and OLE ... does that matter a lot? ...

:-)
ADO uses OLE DB Providers to connect to databases. So no, it does not
matter. ;-)

following is my connection method...

Set objConnection = CreateObject("ADODB.Connection")
objConnection.Open "Provider = Microsoft.Jet.OLEDB.4.0;Data Source ="
& NetPath & dbfile
Set objRecordSet = CreateObject("ADODB.Recordset")
objRecordset.CursorLocation = adUseClient
objRecordset.Open "SELECT * FROM " & tab2 & "" , objConnection,
adOpenStatic, adLockOptimistic

this is the normal way i have handled all the databases.


.... and a fine method it is. This is not relevant to the problem you are
experiencing.

Have you gotten a sql statement for us to look at yet?

--
Microsoft MVP - ASP/ASP.NET
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"


.

Relevant Pages

  • Re: Why not use DAO?
    ... You have been refering to DAO vs. ADO when these two things (in the context ... you must have ALREADY used a provider to get to. ... interface for working with JET databases. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Why not use DAO?
    ... Happy Christmas an fine holidays for you too. ... interface for working with JET databases. ... discussion about that (DAO was also faster as classic ADO) ... universal provider so ofcourse DAO wil outperform ADO in most ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Why not use DAO?
    ... Don't listen to those who say something about your English. ... interface for working with JET databases. ... discussion about that (DAO was also faster as classic ADO) ... universal provider so ofcourse DAO wil outperform ADO in most ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Why not use DAO?
    ... interface for working with JET databases. ... no discussion about that (DAO was also faster as classic ADO) ... more universal provider so ofcourse DAO wil outperform ADO in most ... i just wanted to make clear that you should compare these ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Why not use DAO?
    ... To me your opinion sure does mather, cause as i am not a native English ... interface for working with JET databases. ... discussion about that (DAO was also faster as classic ADO) ... universal provider so ofcourse DAO wil outperform ADO in most ...
    (microsoft.public.dotnet.languages.vb)