LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to Open Source Code Control Project - Perforce

Wahoo.  I figured it out.  Basically, I had my root and view mapping screwed up. 

I had the root set as follows:
c:\Sandbox

And the Depot mapping as follows:
//depot/TestEngineering/LP15/... //njaLP15_Powerage/TestEngineering...


When, what I should have had was the following
Root: 
C:\Sandbox\TestEngineering

View:
//depot/TestEngineering/...  //njaLP15_Powerage/...
0 Kudos
Message 11 of 13
(1,471 Views)
Hi NJA,

Yeah, setting up all the correct configurations is always a little tricky sometimes. Glad everything is working.

Best Regards,
Jonathan N.
National Instruments
0 Kudos
Message 12 of 13
(1,468 Views)

I just want to add a quick comment to this thread.

 

I had the same problem eventhough my path was setup correctly it would always get the SCC_E_INVALIDFILEPATH error.

 

I was able to fix the problem by changing the perforce root directory to use forward slash (/) instead of backslash in the perforce GUI.

 

first it was: c:\work

changed it to c:/work

 

and now I can change between perforce clients/workspaces without a problem with CVI.

-Roy

0 Kudos
Message 13 of 13
(1,276 Views)