|
Home > Archive > MS Access Multiuser > April 2005 > no installable ISAM
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
no installable ISAM
|
|
| Lee Buehler 2005-04-06, 8:05 pm |
| We have several win98 computers on an NT network, some of which we are now
replacing with XP pro machines.
We have several Access97 applications that have front ends on the client
machines and back ends on the NT server. We now receive a "no installable
ISAM" error on the XP machines when we try to run one of the reports. This
particular report option calls a macro that opens the report and then calls
another macro that appends data to a table on the server. It appears that
this is where the operation generates the error.
Temporarily we can get around this problem by running this report from one
of the win98 machines... but we will not have them forever.
| |
| Lee Buehler 2005-04-06, 8:06 pm |
| Today we found additional info and are more confused than ever.
We thought this might be a Windows XP problem, but today we ran into the
same error on one of the Win98 machines and to compound the problem, we
found one XP machine that did not generate the error.
We try to keep the software consistant across the many client machines, by
installing Access97 in it's own folder on each client. When we install
Access, we select all componants.
| |
| Immanuel Sibero 2005-04-06, 8:06 pm |
|
Hi Lee,
Have you checked MS KB on this? Just type in your subject line "no
installable ISAM". You would see many articles that might help you.
An example would be:
http://support.microsoft.com/defaul...kb;en-us;209805
Immanuel Sibero
"Lee Buehler" <lee.buehler@worldnet.att.net> wrote in message
news:eDzwoPeJFHA.616@TK2MSFTNGP10.phx.gbl...
> Today we found additional info and are more confused than ever.
> We thought this might be a Windows XP problem, but today we ran into the
> same error on one of the Win98 machines and to compound the problem, we
> found one XP machine that did not generate the error.
>
> We try to keep the software consistant across the many client machines, by
> installing Access97 in it's own folder on each client. When we install
> Access, we select all componants.
>
>
>
| |
| SteveW via AccessMonster.com 2005-04-06, 8:06 pm |
| I have found this error message one of the most confusing. In some
instances this message is obtained when a connection string to a linked
database is not quite correct. Everything you need may be correctly
installed but if the FE cannot connect to the BE via code because of the
incorrect connection string, then this error will occur.
In my experience of this I have written code to automatically reconnect a
FE to a BE when the FE is opened, if the connect string is wrong 'no
installable ISAM' occurs.
--
Message posted via http://www.accessmonster.com
|
|
|
|
|