Perforce Workspace and LabVIEW

[christophe74]

Hi,

I am taking over a job where I am using an existing PC which has got LabVIEW configured with Perforce for Source Ctrl.

I am using the same local workspace as my predecessor which is simple the c drive.

When I create a new VI and add it to perforce or edit an existing VI, those changes get added onto my predecessor's change list not mine.

The fix is to drag and drop my VIs from my predecessor's change list onto mine but it is a real nuisance.

This only happen with LabVIEW, I use text files. When I check them out they go in my change list without any problem.

Therefore I think the problem comes from LV.

I look into LabVIEW "configure source control", I can't see why the VIs always get checked out into my colleague change list instead of mine.

If anyone has a solution that would be greatly appreciated. 

We are using LV 8.2

Many Thanks,

Christophe 

[nathand · Accepted solution]

Is there a system environment variable P4USER set to the username of your predecessor on that computer?  If so, update it (and possibly other P4 variables) to reflect your name, or delete those environment variables.

[christophe74]

Thanks, there was a login set to my predecessor under "configure source control" then "source control project" . I changed the user to myself and it works!

Many Thanks