My answer was based upon my limited knowledge about this guy's need and knowledge. As far as I understand he is a relative newcomer and I am pretty sure that he is building an aircraft carrier where a row boat would do the job quicker. I have seen people giving him advices earlier which have confused him more than helping him. Too many teachers don't necessary mean better students.

>>>Is there any simple way to enhance the Limit of VFP DBF table beyond 2 GB Capacity ?
>>Follow a few round rules, and this will not be any problem for a normal size application.
>>1. Never use general fields. NEVER!!!
>>2. Never store pictures in tables, only the name of the picture file, with or without path
>
>Both of these guidelines are to be considered based on the system's design. If there's a possibility the data needs will grow beyond 2GB ... then it's likely that FoxPro is not the tool for you. It's too much data to wield easily unless it's just raw lookup data. But if it's transactional where there's 2GB worth of data coming in ... you need another engine.
>
>As for smaller systems, general fields are fine. Storing pictures or other binary data in tables is fine. It's not the best practice, but in some cases it is the most desirable because of the nature of the system.
>
>>3. Normalize the tables, don't add fields which are seldom used.
>>4. Reuse deleted records
>
>Again, determined based on use. Records should never be deleted until there is some rollover process which is designed to explicitly delete them. And when they are deleted they should be removed from the table, not re-used. Until that rollover process is run, they should be marked as deleted using something like an LDELETED table field, so they are identified for audit and datafix purposes (in case there's an error in the program and something is deleted by mistake, it can be easily restored).
>
>Again, this is all determined on use.
>
>The facilities which exist in Visual FoxPro exist to be used. It's bad advice, in my opinion, to advise people to not use them solely because in certain cases they do not perform as well as in other cases. Each case is use dependent. And for most systems that are not huge (less than 500 MB of data total, including history), every facility that VFP provides where there are not known bugs ... it's all fair game for use.