most of the times we do not store dbf/dbc info in verson control, either GenDBC and/or Xml. Xml because there speed is much better than JSON and most of the times the dbf data needed in version control is not large enough to warrant sdf or csv for bulk loading.

>Alejandro,
>
>let me be a bit selfish. http://vfpx.codeplex.com/releases/view/614943 offers a tool that will include in VFP IDE. It let's you regenerate, as Fernando names it, the binaries with FoxBin2Prg from VFP IDE.
>
>It's assigned to
>-quickly create text versions and commit changes (what is the main goal)
>-create binaries from text representation
>
>My approach is as follows:
>
>+ FoxBin2Prg creates file-per-class. Much easier to merge and search.
>+ commit text where usefull
>- this will store pictures and other binary resources as binary, but they rarely change
>- dbf, dbc that belong to the project as binary (there is no use in having them as text, yet)
>+ Using the tool above
>- with FoxBin2PRG to create text and recreate binaries on PJX level from IDE
>- to commit changes to current branch
>- to raise git history (gitk)
>- to raise git shell (git-bash)
>+ do any git related work except straight, backup like commits on bash
>+ Sometimes there is some forward / backward movement on the git side of the problem. If this is finished, I can regenerate the binaries, I do not need it inbetween. For that I do not use git hooks, I rather start it from VFP menu. So automation for regeneration is not my prefered way.
>- OTOH sometimes, when I look for a code snippet, I just do
># generate text, commit
># check out old code
># open the related vc2 file
># copy the code snippet
># paste into vcx
># checkout recent branch
># create text and commit
>-- this is not the most sophisticated way, but much faster then two times binary regeneration
>
>
>>Thank you for the answers Lutz and Craig,0
>>
>>If the binaries are not stored they need to be regenerated when you check out a branch, but only if the associated text file changes during the checkout. Do you know a trick to automate this step? Perhaps git has a hook that makes this easy.