Shiv,

> I too have multiple versions of that dll. I think what really happens is

the

> Microsoft does not stick to its specifications and so vendors would rather
> have the dll local to their applications so they don't depend on the

system

> dll (in C:\winnt\system32). Rightly so !

Yikes. I am familiar with how dll's are found, etc. but it really rubs me
the wrong way to have multiple copies of the "same" dll. I cannot think of
a good technical reason why the latest version of the dll shouldn't work in
all cases. I do realize however here in the real world this is not reality.
It does, on the other hand, fly in the face of one of the main points of
using dll's.

> This is what I am suggesting for the Interbase install. Install it in the
> local folder. That way, we can have other applications running...

Again, I don't like this but I can see where you are coming from.

>
> On one of my servers, I had PC Anywhere and SQL server installed and

working

> fine before I attempted to install Interbase. Both stopped working since.

So

> I had to format and reinstall the OS and other software without Interbase.

I don't follow the format/reinstall. Did you find any other dll's (or other
files) that might be causing this problem?

>
> But it didn't work like that. Neither PC Anywhere nor MS SQL server could
> get rid of that dll. They both complained about the fact that the dll was
> read-only and that I will have to reboot etc. So I did, but they bombed

out

> on re-boot saying they couldn't find the entry point.

MSVCRT was probably in use (by what I don't know). Was InterBase running?
Did you try putting the MSVCRT's that these apps "liked" in their own
directories?

(Sorry if I am asking questions about roads you have already traveled...I'll
do some looking, too.)

Carl