Cross profile pollution: multiple files

[Cory]

I have seen this many times before in Beta and have mentioned it to ISS as well but the circumstances have always been a little suspect so I don't think anyone has taken it seriously. I was wondering if anyone else is seeing something similar or has any idea what's going on.

 

This seems to happen whenever I upgrade to a newer build. This time I know exactly how things were set up and witnessed this so I know for sure something is going on here. On a 2003 Terminal Server with multiple user profiles I have my own profile where I often develop macros for my client. There is a live file for users and a development copy I work in. Both are stored on another file server. In 4.0.0.1 I had all the users set with the option not to launch at startup but I do have a shortcut to their macro file to launch. IE I'm launching the MEX, not the EXE. So before today they are all in the user copy and I am in the dev copy. Perfect. Now today I install 4.0.1.1 and check my MEP and it has only loaded my dev copy. But all the other user profile find both the dev copy and the live copy open on their profiles! This causes all sorts of mayhem. I checked their preferences and MEP is not set to load at startup. BTW months ago I also saw this behavior on a regular Windows 2000 machine.

 

So how is this happening? How does MEP running under user profile A decide to open a file only ever opened in user profile B? Is there something I'm doing wrong or is this some kind of bug?

 

Update: One user reports only having one file open after logging in. This user was not logged on when I did the MEP update.

[joe]

I have seen this many times before in Beta and have mentioned it to ISS as well but the circumstances have always been a little suspect so I don't think anyone has taken it seriously. I was wondering if anyone else is seeing something similar or has any idea what's going on.

 

This seems to happen whenever I upgrade to a newer build. This time I know exactly how things were set up and witnessed this so I know for sure something is going on here. On a 2003 Terminal Server with multiple user profiles I have my own profile where I often develop macros for my client. There is a live file for users and a development copy I work in. Both are stored on another file server. In 4.0.0.1 I had all the users set with the option not to launch at startup but I do have a shortcut to their macro file to launch. IE I'm launching the MEX, not the EXE. So before today they are all in the user copy and I am in the dev copy. Perfect. Now today I install 4.0.1.1 and check my MEP and it has only loaded my dev copy. But all the other user profile find both the dev copy and the live copy open on their profiles! This causes all sorts of mayhem. I checked their preferences and MEP is not set to load at startup. BTW months ago I also saw this behavior on a regular Windows 2000 machine.

 

So how is this happening? How does MEP running under user profile A decide to open a file only ever opened in user profile B? Is there something I'm doing wrong or is this some kind of bug?

 

Update: One user reports only having one file open after logging in. This user was not logged on when I did the MEP update.

 

Not sure if this has anything to do with it, but whenever an update is done all of my Macro Explorer column settings revert back to some sort of a default as if they were never saved. So maybe your problem is things are getting removed when a new install is done, too. I am only making a wild guess here. Grasping at straws as it were.

[Cory]

Well you touch on another problem of mine regarding upgrades. In the beta days I would see partial setting reversions from time to time that didn't make a lot of sense. Since formal release it seems to have gone away. But MEP obviously remembers which files you had open somewhere but what concerns me is that all the local settings should be isolated to that users profile. I mean each person has their own HKCU and file area. So how's this happening? Anyway thanks for the input.