OF ALL THE %$#%^@ whats wrong !! 1

[TRYP]

i am in a world of confusion.

i have 3 files
1.) accessFrontEnd.mdb
2.) accessBackEnd.mdb
3.) accessWorkgroup.mdw

i need to get at tables in file #2.
i have used ADO many time to date but i am getting error after error. i think im dumb now.

i cant even seem to open the darn DataBase

CODE:

Private Sub Command1_Click()
On Error GoTo errorhandler

Dim conn As ADODB.Connection
Set conn = New ADODB.Connection

Dim recs As ADODB.Recordset
Set recs = New ADODB.Recordset

conn.ConnectionString = "persist security info=false;" & "provider=microsoft.jet.oledb.3.51;" & _
"data source=d:\pensacola\PENSACOLA00d.mdb;" & _
"pwd=password;" & _
"uid=user;"
conn.Open ""
MsgBox "open"
recs.Open "select * from table", conn
MsgBox "recordset"
Exit Sub
errorhandler:
Text1 = Err.Number & " " & Err.Description
End Sub


I get this error :
-2147467259 Couldn't find installable ISAM.

Earlier i had various other messages.

PS it errors before either message BOX

-tryp (frustrated)

 

[dpaulson]

Did you make reference to the ActiveX Data Objects Library?
David Paulson

 

[TRYP]

yes
ado 2.5
-tryp

 

[culshaja]

Use the Jet.4.0 Driver its far more stable. If that doesn't work install the newest version of MDAC as it can get its self in a bit of a tizz!!!

James James Culshaw
jculshaw@active-data-solutions.co.uk

http://www.active-data-solutions.co.uk

http://www.brainbench.com/transcript.jsp?pid=193305

 

[dpaulson]

Dim strconnect as string
strconnect = "persist security info=false;" &"Provider=Microsoft.Jet.OLEDB.4.0;" & _
"DATA Source= d:\pensacola\PENSACOLA00d.mdb;" & _
"User ID=user" & ";Password=password"
conn.Open strconnect

Try that


David Paulson

 

[TRYP]

now i get this error :

-2147217843 Cannot start your application. The workgroup information file is missing or opened exclusively by another user.

:frustrated:
-tryp

 

[Quehay]

Is it a customized mdw with groups/permissions for this db or the standard system mdw with Admin user default? If the latter then a new copy of system mdw should get it going. Hopefully you have a backup copy if the mdw is a customized group. Access security is such a pain that I wouldn't go beyond database level password unless the users group is a single stable entity. Good luck--be sure to post in the Access forum as you'll get the benefit of those who are very experienced in solving this!!

 

[TRYP]

OK
i finally began talking to the database.... the workgroup file had a different name than the default sooo it had to be referenced in the command string....no big deal but finding that little tid-bit of information was like pulling teeth out of a crocodile......

connection.Properties("Jet OLEDB:System Database&quot ="filespec"

some "hidden" and "secret" stuff LOL LOL

anyhow... does anyone know if you can query a recordset ???


- tryp