I have not been able to get the Send To to work, doing it generates a VFP error that it cannot locate foxbin2prg.exe

>Sounds good, going to give it a try.
>
>>>I do not have the time nor money to switch now to something else. SOS has always done great for me, so while I might switch at some point, I cannot right now.
>>>
>>>Here is my question:
>>>
>>>In SOS I can set command lines for File Compare Tool, folder compare tool, and merge tool. The defaults use diffmerge like this:
>>>
>>>%sos_dir%\DiffMerge.exe /ro1 /ro2 /title1=%t2 /title2=%t1 %2 %1
>>>
>>>And I have these params available:
>>>-working folders file
>>>-latest remote file
>>>-baseline
>>>-merged copy of working folders file
>>>- titles of file 1, 2, and 3
>>>
>>>
>>>
>>>SOS has a decent superset of functionality. It seems that given that functionality, it should be possible to have a script that does the merge and then calls foxbin2prg to recreate the binaries.
>>>
>>
>>Ok, if SOS have this parametrization then you can do something with it. You can do a VFP program to interface between SOS and the merge tool, so your program-interface receives the parameters from SOS, call the merge tool with this parameters *and* finally autogenerate the binary from the selected text file.
>>
>>Something like this:
>>
>>

>>* VFP9_SOS_Merge_Interface_Txt2Bin.prg
>>LPARAMETERS tcMergedFilename, tcP1, tcP2, tcP3, tcP4, tcP5, tcP6
>>
>>%sos_dir%\DiffMerge.exe tcP1, tcP2, tcP3, tcP4, tcP5, tcP6  && You need to make a valid Run call, this is only example
>>
>><foxbin2prg_dir>\foxbin2prg.exe tcMergedFilename
>>

>>
>>In this example, the first parameter is just for FoxBin2Prg, the remaining parameters are passed to DiffMerge.
>>Finally, compile as EXE, soy you can put in in SOS.
>>
>>I think this will do the job.