>>>Is the latest version in the VCX or the text file? What happens if I check in the text file instead of the VCX? What happens if one developer makes changes in the text file and forgets to put the changes in place, then another makes changes to the VCX or even a different text file of the same class library?
>>
>>You still don't get it.
>>
>>It's not *OR*. There's only ONE "Source File".
>>
>>You know; like .C, .BAS, >>> .PRG <<<.
>>
>>And let's not start the "I don't want the code Forms in PRGs" circle again; just keep repeating: "two-way", "two-way", "two-way", ...
>
>That my point. If I make changes to the text file, then don't apply the changes to the VCX and check in the VCX, another user will grab it and make their changes. We already have enough problems with just the VCX. I don't need more.

Here we go-round the mullbery bush, mulberry bush, ....

Repeat the following as often as necessary:

>>You still don't get it.
>>
>>It's not *OR*. There's only ONE "Source File".
>>
>>You know; like .C, .BAS, >>> .PRG <<<.
>>
>>And let's not start the "I don't want the code Forms in PRGs" circle again; just keep repeating: "two-way", "two-way", "two-way", ...

IE. >>>>>>>>>> THERE IS NO VCX/SCX/MNX ! <<<<<<<<<<<<<<<<