>>You're being kind, especially when talking about class libraries, forms and
>the like.
>
>Oh I know but don't want to scare him off :-)

The real solution here is to use VSS as a tool one way - if you want to use the VSS integration with VFP and VFP projects, then make certain to use the VFP interface, at least to deal with VFP-related things. If you want to check stuff in and out by hand, do it with VSS's SourceSafe Explorer, which you can access from within VFP, but doesn't have the automatic integration with the Project Manager. The best way to screw things up is to mix'n'match; one mistake and things can and probably will get out of sync. The biggest issues seem to arise from files handled through SCCTEXT, since they're the basis for checkin and checkout of the semi-binary (can't think of a better term) VFP source things, and they're only generated by SCCTEXT.