>OK - well we have added the project to source-safe by selecting the main program file and from the project menu "Add to Source-Control" - we have also enabled "Multiple Checkouts" in VSS Administrator but still get "File Access denied if either one of us opens the project and then the other attempts to open it afterwards (ie. the second user opening the project gets the error)
>Any ideas greatly appreciated...
Chris, I'm not sure whether Multiple Checkouts is the solution for this problem. Multiple Checkouts uses the Merge facility and that's not really suitable to binary data.
In the vfp7-documentation I read: "When working in a team development environment, developers don't share the same project files (.pjx and .pjt files). Instead, developers maintain their own local copies of the .pjx and .pjt files."
Each developer has a really local PJX and in addition a PJM file. That's a text file that denotes the differences between the local PJX and the project file info in VSS. Read on in the vfp-doc if you want to use the pjm-method.
What WE do here might not be the 'official' method, but we have our reasons for doing it this way:
Also Check In de pj? files. Then Get Latest Writable of those same files. All developers can do Get Latest Writable. If a developer wants to modify the list of files that's handled by the pjx, then a (single) Check Out is required, followed of course by a Check In after the modifications were done. Other developers should then redo a Get Latest Writable.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
