MSADO21 Error - please assist...

Yeah, but if you can claim it's a network issue, then you can hand the problem over to the sysops....sit back....and drink coffee, safe in the knowledge that some one else's ass is in the sling;)

Ok off to msdn, will try to find something there for ya...

I don't really need to blame anyone today, but I'll keep that in mind... ;)

Cheers.

Ok this is the only reference l got on my search

http://support.microsoft.com/directo...h_SRCH&SPR=ADO

Log in and have a look, hopefully the answer is in there;)

Quote:

---

STATUS
Microsoft is researching this problem and will post new information in the Microsoft Knowledge Base as it becomes available.

---

Dickheads...:mad:


This was in reference to a specific DB (advworks) or something, but I reckon it may be the same problem.... shall continue looking...

Quote:

---

Originally posted by rjlohan
But it works on other virtually identical machines... :( Why would changing the provider make a difference?

But I shall keep it in mind...

As for 2.5, I don't know if I even have that anymore - when I installed MDAC2.7, I lost references to earlier versions... :eek:
And anyway, 2.5 was always giving me stupid problems when distributing...

---

No you said that some machines have 2.7 some have 2.1 some have 2.5!
Changing the provider to the one mentioned might help because that provider will work with all mdac's released!!

Is this an access or SQL database??

Access.

I thought that MDAC2.7 would be installed on those machines, since I have references to it in my project... am I mistaken?

Ok another thought, pop into the Access db and compact it maybe....could be corrupt if stand alone???? Though you would probably get an unidentified db sort of error l guess.

Gotta Log,

Cya Later....

Try connecting using ADO and Jet the usual way! You know Set cn as new.adodb connection blablah!!

Does that work?

If so you can round it down to a few things!

later
b :)

Quote:

---

Originally posted by Beacon
Try connecting using ADO and Jet the usual way! You know Set cn as new.adodb connection blablah!!

Does that work?

If so you can round it down to a few things!

later
b :)

---

As opposed to what? I thought that's what I was doing...
:confused:

as opposed to this:

VB Code:

Option Explicit
Private cn As ADODB.Connection 
Private rs As ADODB.Recordset 
 
    Set cn = New ADODB.Connection
    cn.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;" & _
      "Data Source=" & App.Path & "\MYDB.mdb"
    cn.Open
    Set rs = New ADODB.Recordset
rs.open "SELECT * FROM TABLENAME ;", cn, adOpenKeyset, adLockPessimistic, adCmdText

I never connect like that.
I use

strConnectionString = "..."

cnn.Open strConnectionString

etc. etc.

Same dog different tree!

Try it butmunch!;) :p

Try which?

I use this:

[code[]
Set cnnExamCentre = New ADODB.Connection
Set rstExamCentre = New ADODB.Recordset

'Open database connection
cnnExamCentre.Open strConnection
:
:
:
'Close database connection
cnnExamCentre.Close
[/code]

Try anyone that is different to the one you posted earlier in this thread!

...Which means you can't register them via RegSvr32.exe or anything else.

Usually what I do is just chuck them in the %WinSysDir% or in this case, the %Common Files%\System\ADO and they work ok.

Maybe try a simple DAO connection to narrow down the possibilities.....

Was trying this today...but my friggin data disk has disappeared into the ether....

Just to help out

Starting with 2.1, and then try 2.7, may or may not get the same problem, but if l do can hand it off to some of the resident MS specialists in the office...

I haven't solved it yet, mind you I have put it off temporarily for more URGENT work... :p

Found this on a software companies site for faq. Sounds similar so it's worth a shot.

E11. [S1000][Microsoft][ODBC Access 97 ODBC Driver]General error Unable to open registry key 'DriverId'.
This exception happens when the ODBC data source you setup for your Access database contains certain security protection such that an NT background service like IDS Server is not able to read. The solution is to run the IDS Server using your own user account (See FAQ-G14).

G14. How to run IDS Server using a specific user account on Windows NT?
By default, IDS Server on Windows NT is run as a NT service using the default 'system' account. This account has minimum security, network and other customization. Sometimes it is necessary to run the IDS Server service using a specific user account so that the server inherit configurations such as ODBC data sources and network drive mappings setup using that account. Here is how you can do it on NT 4.0:

1. Run Control Panel - Services, find and highlight the IDS Server service and click on the "Startup..." button.

2. Select the "This Account:" radio button, then type in the user account in the edit box to the right (for example administrator or informix). Then enter and confirm the Windows NT password of the selected user account in the two remaining edit boxes.

3. Click "OK". Stop