TYPE MISMATCH OPENING RECORDSET

This code looks good, do you know for sure which line is producing the error?

Is this code a sub or a function? You could possibly be having trouble with the return value if it is a function.

The error appears upon executing the openrecordset() function when using the debugger.  When it error trapping, it jumps to the error handler after that line.  It is not a function but a sub called GetOptions(), which is called in the very first line of Sub Main.  

Perhaps what is in order here is a second question:  how can I be sure the OpenDatabase command actually worked?  I was thinking it must have worked, or I would have gotten a different error after the OpenDataBase().  Now I am not so sure...

Sorry to mislead everyone about the sub vs. function issue...  

To see if it works.. you can do this..
Set dbOptions = wrkJet.OpenDatabase("SysOpts.MDB", True)
msgbox dbOptions.Properties(0)

it should print the path of your connection

What means "Systems Options" ?

If it is nothing, you must fill in OpenRecordSet with SQL .

ex> "SELECT * FROM [Table] WHERE [FIELD] = 'aa'"

SystemOptions is a Table in SysOpts.MDB.  Using the suggested SQL vs. the table name generated the same error.  

AnswerMan, the msgbox.dbOptions.Properties(0) is a handy thing to know, thanks.  Yes, the DB is open.  I think it must be *where* I am trying to do this from and will place the code under a button on a form and see if it works there.

Further info:  it's not that I am trying to execute the code before showing the Main form.  It doesn't work anywhere.  This is a real mind bender, because I have used this code before.  Also, yes, the table exists, and it's the correct name.  I have also tried changing the name of the table.  

using the same technique.. can you connect to the standard NWind.mdb database?

What version of dao are your running?

Strangely, this code works:

    Dim wrkJet As Workspace
    Dim dbOptions As Database
    Dim rsOptions As Recordset
    Dim sTableName As String
    sTableName = "SystemOptions"
    Set wrkJet = CreateWorkspace("", "admin", "", dbUseJet)
    Set dbOptions = wrkJet.OpenDatabase("c:\VBGenDB\SysOpts.MDB", True)
    With dbOptions
        .OpenRecordset (sTableName)
    End With


Go figure!

Anyway, thanks.  

Nevermind, it does buy me anything.  

Using the TypeName() function VB informs me that wrkJet is a Workspace, that dbOptions is a Database, but that rsOptions is "Nothing"...

That would explain the type mismatch.

If you have references to two different libraries that have a recordset object, you may have a definition to the wrong one.  Say you have ActiveX Data Objects and DAO referenced in your project, then maybe it is trying to use the ADO recordset object.  With ADO, you have to Dim with a new, otherwise it is equal nothing (its just a pointer).  Maybe in your Dim statement you should specify which types you are using by prefixing them with DAO.  Like DAO.Recordset.  That may fix your problem.

Later,
Martin

This code *does* work.  What confuses me is that VB did not type myRecordset as a Recordset with using the Dim myRecordSet as Recordset statement....  Ah, well.  

    Dim myRecordset As Variant
    Dim wrkJet As Workspace
    Dim dbOptions As Database
    Dim sTableName As String
    sTableName = "SystemOptions"
    Set wrkJet = CreateWorkspace("", "admin", "", dbUseJet)
    Set dbOptions = wrkJet.OpenDatabase("c:\VBGenDB\SysOpts.MDB", True)
    Set myRecordset = dbOptions.OpenRecordset(sTableName)
    With myRecordset
        bPasswordSecurity = ![PasswordSecurity]
        bUseageLog = ![UseageLog]
        bScanForRequiredFiles = ![ScanForRequiredFiles]
    End With

I think you have hit on the problem, Martin.  Thanks...

many times using a database u get the type mismatch error when a table in your is accessing the wrong type of data specified for that particular field.

First use the Data control on your form to select the datbase U want to access and then declare the variables for workspacem, database and recordset as global. then no error will occur. I have tried it. Make the data controls visible property as false  at runtime.