>Do I understand you read the compiled stuff (objcode) for the prg's, not methods field?

I don't do magic :D I read the methods's field code


>
>If methods then just split (by record copy) -> create the prg

I already do something like that, but it's not so direct as copy method into prg, because some metadata needs to be write in place so later you can regenerate the binary. Method's code have not all the necesary stuff, but have the most part, the remain is on the rest of vcx/scx fields.


>
>and backwards
>
>create the prgs (without objcode), add them up to the original large vcx and compile those.

As the last one, can't do that directly because of the metadata and because I must parse the code, but the workaround to simplify the logic was to merge all the tx2 files in one, as FoxBin2Prg expects, and then process it normally.


>
>To forget one? Depends on the system you use.
>If git :
>A proper set .gitignore file
>* -Run your code, create all the little files
>* git add .
>*git commit -m "yourcomment."
>-done
>
>backwarts?
>
>*git checkout ...
>*run your code
>-done
>
>there is no way to loose a file ....
>
>But this the way git works, it's allways a snapshot of the whole subtree. You can not check out single files in that sense. It's just all or nothing, Bit strange if one come frome VSS and the likes, but its working.

And that's the story: Git works this way, adding all the files under the project directory and subdirectories, without exception, but all other SCMs/DVCSs don't do the same.
Plastic, in example, just add the files you tell it to add, and don't add all inside directories, which remains as "private" files.
Good thing of this approach is that you can use you workspace with data and with your testing programs (or even your temp progs), and you aren't forced to add all of this to source control. That's why is better that anyone choose the best option for the SCM/DVCS he/she is using.


Regards.-