Runtime Error 3170

[Guest]

The error message says "Could not find installable ISAM". but I just did a
full install of Access XP?!?!? All I know is that this error is preventing
me from linking to excel or textpad and most importantly, I can not export to
excel or textpad!!!

Can someone please help?

Johnny

 

[Guest]

There is a previous post on the subject, by Jeff Conrad

See if this link offers some guidance:

http://support.microsoft.com/kb/q171955/

 

[Guest]

Just have a look on the thread

http://www.microsoft.com/office/com...orms&mid=a93cba95-285d-4f6c-90d2-65088ea81812

 

[Guest]

Your awesome!!!! Looks like in Access XP I just needed to re-register the
appropriate dll's that corresponded to excel and text. Solved my problem in
a jiffy!!!! Appreciate the help!!!!

Johnny
Access Addict

 

[Guest]

I have a slightly different problem with linking an Excel table to Access.
I am able to link the Excel table using the tool bar > get external data >
wizard. I don't get the error 3170.

However I have a line of code: "dbsTemp.TableDefs.Append tdfLinked"

within the below, which gives the 3170 error.

Sub test()

Dim dbsTemp As Database
Dim tdfLinked As TableDef
Dim rstLinked As Recordset
Dim intTemp As Integer
Dim strTable As String
Dim strconnect As String

Set dbsTemp = CurrentDb()
strTable = "ExcelTable"
Set tdfLinked = dbsTemp.CreateTableDef(strTable)

new1 = InputBox("Enter a data sheet name to create")
new2 = new1 & "_Data"
new5 = "Data for " & new1 & " Valves"

strconnect = "Excel 2003; Database = O:\9210L\Works\A353\MATERIALS\SP\" &
new5 & ".xls"
tdfLinked.Connect = strconnect
SourceTable = "Data1"
tdfLinked.SourceTableName = SourceTable
dbsTemp.TableDefs.Append tdfLinked

new3 = new1 & "_Note_tbl"
DoCmd.CopyObject , new2, acTable, "Ball_Note_tbl"
new4 = new1 & "_Notes"
DoCmd.CopyObject , new2, acTable, "Ball_Notes"
End Sub

Will I have to do the methods under the links in there as well?

Sajit

 

[Guest]

I tried the method 2 under the link http://support.microsoft.com/kb/q171955/

The re-registration of the dll associated with the Excel table, MSEXCL35.DLL
registered successfully.

But the error still happens.

Is this not something MS should come up with a patch rather than making the
user go through all these long steps.

Sajit