> The problem is that even if it is, you can be in a
> situation where you have an old DLL loaded but with
> new script running.
>
Yeah and this certainly seems to be the cause of the majority of the
errors being reported.. But my belief is that if the new DLL has a
different version, and the new version is registered, regardless of
the loaded state of the old version, then the dll and search
versions should match and everything will work... it is a perfect
world isnt it? :-)
>I don't think I'm convinced that logout/login is a certain remedy.
For me, the logout/in works every time at home and the office... I
have never had a problem installing a new version where anything
more than a logout/in was required.. I did however observe a problem
on a relatives machine recently where the logout/in didnt do the
job. I think some OS dependencies are at play.. She was running
Win98 and I am running Win2k... If I remember right we actually did
an uninstall/reboot/install to get things cleaned up properly...
Monty
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/
Monty Scroggins
Broadband Data Systems Engineering (BDSE)
MCI Worldcom
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Dqsd-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dqsd-users
http://sourceforge.net/mailarchive/forum.php?forum_id=8601
