Can't find installable ISAM

Here's my code:

Option Explicit
Dim ws As Workspace
Dim dbCurrent As Database
Dim rsCurrent As Recordset

Private Sub Command1_Click()
    Dim tmpTable As TableDef
    Dim Fld As Field
    Dim i As Integer

    Set dbCurrent = ws.CreateDatabase(App.Path & "\temp.mdb", dbOpenDynaset)

when it gets to this last line, it gives me an error saying "Can't find installable ISAM," which is strange because I was able to run similar code yesterday.
LVL 32
Who is Participating?
plqConnect With a Mentor Commented:
dbOpenDynaset applies to the openrecordset method, not to createdatabase
You can try:

Dim catCatalog As New ADOX.Catalog, tblTable As ADOX.Table, colColumn As ADOX.Column

catCatalog.Create "Provider = Microsoft.Jet.OLEDB.4.0; Data Source = " & Database

set tblTable = New ADOX.Table
tblTable.Name = "MyTable"

set colColumn = new ADOX.Column
colColumn.Name = "ColumnName"  '**
colColumn.Type = adVarWChar    '**
colColumn.DefinedSize = 50     '**
colColumn.Attributes = adColNullable  '**  - this still does not set Allow Zero Length Attribute to Zero (it only sets Required to False)

tblTable.Columns.Append colColumn   '**

'** repeat the code to add as many columns needed.

'for columns like datetime you don't need DefinedSize

catCatalog.Tables.Append tblTable

set tblTable = nothing: set colColumn = nothing: set catCatalog = nothing


The DLL for an installable ISAM file could not be found. This file is required for linking external tables
(other than ODBC or Microsoft Jet database tables). The locations for all ISAM drivers are maintained in the
Windows Registry. These entries are created automatically when you install your application. If you change
the location of these drivers, you need to correct your application Setup program to reflect this change and
make the correct entries in the Registry.

Possible causes:

An entry in the Registry is not valid. For example, this error occurs if you're using a Paradox external
database and the Paradox entry points to a nonexistent directory or driver. Exit the application, correct the
Windows Registry, and try the operation again.

One of the entries in the Registry points to a network drive and that network is not connected. Make sure
the network is available, and then try the operation again.
DrDamnitAuthor Commented:
My, how sometimes the obvious eludes us....
I know the feeling. Thanks for the points.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.