×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I just noticed the problem again. I don't know that I have all the pieces
exactly in place, but here's the basic scenario: I have multiple connections
to the same machine (basically with different user profiles and/or library
lists). My default connection is not connected (I call it the default,
although I'm not sure there is such a concept -- it's the first connection I
defined), but one of my other connections is connected. In that scenario,
the following behavior occurs:
1. I use RSE to delete a member in my filter, and after the warning about
deleting a real resource, WDSC pops up the signon dialog attempting to
connect my default connection. I can enter the user id/password, at which
point it connects (and runs my startup program) and then deletes the member,
or I can hit Cancel, and it just goes straight on to the delete.
2. A similar thing happens during a copy or add of a member, or a delete of
an object. At some point in the process, a dialog pops up to connect to the
default connection. You can hit cancel and the process completes, but that
means the dialog will appear every time you do one of those operations.
Joe
From: Brian Parkins
I must have been having a Monday on a Tuesday....
I get more than my share of those too, Joe. WDSc has that affect - all
those different Perspectives <grin>.
midrange.com
