Did you check the forum for Vault? They have a great online forum. When I had the same experience, reinstalling the Vault client fixed it...


>Thank you very much for the suggestion. Because of it I started a small project with 2 prg files and discovered that I am able to interact with Vault form the IDE in my home computer but not the one at the office, and also not from another machine at the office. So now the detective work starts.
>
>Do you have any suggestions of what settings may cause problems?
>
>Thanks for the help.
>
>Alex
>
>
>>>So you save "clear text" version in database and not scx, vcx, frx?
>>>
>>>Christof's code is nice and simple.
>>>
>>>Still have the problem that VFP shuts down when I say that project is under source control. Any suggestions?
>>
>>Don't have the project under source control. Vault (or any other) integration is tricky - for those for whom it works, nice, for the rest of us, manual does it.
>>
>>First of all, have a clear text version. We do it (using scctextX.prg) in parallel to the dbf version, just so we can diff and maybe merge as needed - or so we can steal code from our own classes without exactly knowing the class, library suffices. Generally the text serves to check for differences on scx and vcx files.
>>
>>My algorithm:
>>- check out the files I need (not necessarily all at once - I can't know everything in advance)
>>- work
>>- when I'm ready to check in, run a little script to generate all the .scc files in batch (well, it should do so for updated only, but for some reason it seems to calculate a different sys(2007) on the OLE field on some (not all!) activeX controls, so the scc comes out as different.
>>- at check in, go through the "pending change set" tab in the lower part of the client. Vault knows what I checked out, I don't have to remember. I may want to check some things in now, some later; may want to check one set of files now with one comment, then another with another comment. Select, write the comment, check in (scc files go together with the files from which they were derived!).
>>- when nothing more checked out, get latest on the whole tree, with overwrite. That'll also overwrite any stray versions which were falsely made different by compiling (or the damn OLE field).
>>
>>Rule of thumb: if you've edited it, you've checked it out first (or immediately after). You did get latest without checkout, you overwrote your changes - your bad. You're the cow which kicked the bucket.