>George, you're not giving me a warm fuzzy here....and it's confusing (and frustrating) all of us here. I can reproduce the error in development, but if I'm already attached to the data server, it works fine. If I'm not - I get the same error that the user does. I've checked for any IPC's that might be running - but that was a dead end.....

Dorris,

Sorry about the lack of "warm fuzzies" but I'm almost out of meds, and don't know when Raoul Duke is going to send me a "CARE" package. He's been in mourning ever since last December and that makes him doubly difficult to reach, which is normally next to impossible.

But I digress...This reminds of a problem I had for awhile. If this sounds familar then we may have a clue to the solution.

Recently, we changed from Novell to NT servers. Which, of course, caused more problems than any sane person might care to deal with. But, hey, that's why we're in this business and not quite sane.

Anywho, I normally don't run login scripts (principally because of Novell, but that's another issue). I normally, log into the work station (W2K) then the network. However, the change to NT meant that I had to log into the domain as well. Now in order for me to map to another server either through the map dialog or WSH I have to modify how I send the user name: I precede it with domainname\. So when I log in or use the WSH my user name becomes: domainname\gtasker.

Here's another little tidbit that makes me think this might be the same problem. If I'm already mapped to a particular server, I can, from the map dialog, log another instance without having to provid the username and password again.

So to summarize, check to make sure that you're logged into the domain.

Sorry about carrying on like this. I gotta go find Raoul.