Chuck
I remember having a similar problem some years ago - one day I
couldn't import Excel files. A cry for help here got me this info:
I recommend re-registering the following two files. Note that the path
to
each file may be different on your PC. To do this, click on Start >
Run. Then
copy each of the statements shown below, one-at-a-time, and click on
OK:
Regsvr32.exe "C:\program files\common files\microsoft shared\dao
\dao360.dll"
Regsvr32.exe "C:\program files\common files\system\ado\Msado15.dll"
Optional, but won't hurt is to make sure that dao350.dll is also
properly
registered:
Regsvr32.exe "C:\program files\common files\microsoft shared\dao
\dao350.dll"
If a library is marked MISSING, click the Browse button, and locate
the correct file for the library. The table below lists the files for
the crucial libraries of your version of Access.
If the library is not even shown, you may need to re-register it.
Click the Windows Start button, and choose Run. Enter regsvr32
followed by the full path of the library file. Include quotes if the
file name contains spaces, e.g.:
regsvr32 "c:\program files\common files\microsoft shared\dao
\dao360.dll"
Occasionally, the problem is not solved until you unregister the
library and re-register it. Uncheck the missing library in Access.
Close Access. Issue this command, and then the one above to re-
register it:
regsvr32 -u "c:\program files\common files\microsoft shared\dao
\dao360.dll"
Re-register it (as above). Open Access, and select the library
reference again.
********THE FOLLOWING IS WHAT WORKED FOR ME********
"Sounds like your DAO library got un-registered somehow. (Office 97
installation doesn't register it properly in the first place, so
re-installing is no help.)
Go to Start menu|Run, type the following, and click OK:
regsvr32 "C:\Program Files\Common Files\Microsoft
Shared\DAO\dao350.dll"
You can also check to make sure your references are ok (open any code
module, go to Tools menu|References, and make sure nothing is marked
"MISSING").
If I remember rightly this came from a wonderful lady named Martha and
it saved my sanity!
HTH
Jeff B
I gave up trying to get the proper files in the value pack installed in the
right directories in the C drive. I restored the complete C drive from my
backup.
No data files are on the C drive so I didn't have to use my incremental backups
to get my data files up to date.
Chuck
--
> I gave up trying to get the proper files in the value pack installed in the
> right directories in the C drive. I restored the complete C drive from my
> backup.
> No data files are on the C drive so I didn't have to use my incremental backups
> to get my data files up to date.
>
> Chuck
> --
I ran into that problem earlier this year. Some registry entries got
deleted somehow. I think they were the ones in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\ISAM Formats\
I was able to bring back most of the import/export types by fixing
those entries by comparing with the registry settings on another
machine running Access 97. That seemed not to fix everything
perfectly so I think I wiped Office key references, folders, etc. out
of the registry entirely and did a clean install of Office (after
noting that simply reinstalling or fixing Office without changing the
registry did not allow the Access installation to write the correct
ISAM folders/entries into the registry -- don't ask me why). Merely
restoring the registry from a previous point might have solved your
problem. Also, note that is better not to choose "SQL Server" as an
option when installing Access 97 unless you really need it.
James A. Fortune
CDMAP...@FortuneJames.com