petreco,
Just to add to this discussion, you should know that unlike Access, that keeps everything in a single file, FoxPro in all it's versions, keeps things separate. The "database" refered to in the older FoxPro documentation is actually a single table (.DBF) and optionally may include an associated .CDX (compact index) file and/or a .FPT (memo text) file. [For the purists, there may also be 0 -> n .IDX index files also.] Even the VFP database container (.DBC) is actually a table that has links to all the actual tables and indexes - they are really not "contained" in it.
Most all the pieces that are used to generate an .EXE file, are also tables - Menus (.MNX, MNT), Reports (.FRX, .FRT), Labels (.LBX, .LBT), Screens/Forms (.SCX, .SCT), Projects (.PJX, .PJT) and the VFP Class Libraries (.VCX, .VCT). Programs (.PRG), Include files (.H), etc. are used as is. Note: Depending on the version of FoxPro/VFP, some of the table components are used to generate intermediate "program" code, while others are included and "run" directly by the runtime.
The current (VFP 7.0) file layouts are well documented in the program documentation available on the MS MSDN site. Start at
and then click on General Reference and then File structures.
Rick