Hi Gerhard:

>Why do I have to check the capitalization?
>In your example most of the files an directories are spell lower case, but MAIN_PROGRAM.PRG ist spellt upper case. What should I use?
>

The default configured capitalization in FoxBin2Prg is intended for file extensions (EXT vs ext), to keep them in lowercase, using this config in filename_caps.cfg:

filemask=*.*:N.L

But you can configure the full name capitalization for better normalization, using something like this config:

filemask=*.*:M.L

or even can configure capitalization by extensions:

filemask=*.DBF:L.L

(Inside filename_caps.cfg there is a short explanation of this)

The need of the capitalization es because Plastic is multiplatform, and because can use various BDD as beckend (SQLCE, SQL Server, MySQL, PostgreSQL, etc), and in all platforms --except Windows-- file names are case sensitive, so in Linux or Mac THISFILE is not the same as ThisFile or thisfile, more precisely, they are 3 different files that can exist on the same dir, while Windows overwrite each one with the last file you copy.

Because of this multi-platform case sensitive thing, filenames are saved in the BDD with the specific case it have on disc, so you can be in the case of having THIS.SCX and this.scx as 2 files, when in Fox for Windows they are the same. (In old Fox for Unix thay was different files). So for not messing with the source code stored in BDD, a normalization is necessary.


>I used VSS up to now. Do you recommend to delete the old ??a files vreated by VSS like *.mna or *.sca?
>

Absolutely yes! You are changing the SCM tool (in this case to a DVCS tool) and you wan't confuse the old files with the new ones, because they are different in content. Old *.??a files have a Row Data copy of memo content of scx,vcx,etc while the new *.??2 files have PRG-Style code for scx,vcx,etc and XML-Style for DBF,DBC,FRX,etc

*.??a files are only necessary when using the SCCAPI integration with FoxPro (as used by VSS) because it expects those extensions, but when changing to a better SCM/DVCS tool, I strongly don't recommend using this API (specially the old 1.0 spec), because you loose functionality and you wan't the old blocking scheme of working with files.