Jim Dettman
jimdettman at verizon.net
Sat Jul 16 09:33:56 CDT 2011
Rocky, Depends on version, but in the past, corrupt registry entries was usually the cause (assuming this was working already). See: When you import files, export files, or link files in Access 2002 or in Access 2003, some file types are missing, or you may receive a "Could not find installable ISAM" error message http://support.microsoft.com/kb/283881 This type of problem was the same all the way back through A97 (different registry keys though). Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin Sent: Wednesday, July 13, 2011 07:25 PM To: accessd at databaseadvisors.com Subject: [AccessD] VBA run-time error 3170: Could not find installable ISAM A prospect is getting this error: VBA run-time error 3170: Could not find installable ISAM When I do TransferSpreadsheet. Does anyone know offhand what the likeliest cause of this is? MTIA Rocky -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com