>I would have given the same answer earlier. But since I have got the impression that Harsh is relatively new to VFP, I didn't want to involve even more new stuff.
>
>I didn't work with SQL server at all before my period on Aruba. There I learned to use SQL server, and since I came home I have been busy reading and building my own framework. The more I use it the more I like it.

SQL Server pretty much addresses any stability/capacity/programmability issues that dogged DBFs and DBCs from the beginning.

The server itself has some overhead on whatever machine it is installed, but the performance is outstanding.

It is a considerable shift from the DBF/local table operation, but once you get over the hump, you don't look back.

It also makes it a lot easier to switch front ends if desired.

>
>>>Forget about that approach, you are only creating problems for yourself. Either you follow some of the tips I gave you, or you use for instance MSSQL server as data storage. I do the latter, it's much more stable, it's faster with many users and it's expandable. I now only use DBFs for some lookup tables which I include in the exe, for everything else I use SQL server and cursors.
>>
>>Now you're talking!
>>
>>>
>>>>Sir,
>>>>While Searching on Google I found some Information on how to increase the data size over 2GB, but dont have still Evaluated that. Here is the link.
>>>>
>>>>
>>>>http://devzone.advantagedatabase.com/jeremym/fox_large/foxprolarge.html
>>>>
>>>>
>>>>AND
>>>>
>>>>
>>>>http://devzone.advantagedatabase.com/dz/webhelp/advantage10/index.html?devguide_connecting_to_advantage_using_the_advantage_odbc_driver.htm
>>>>
>>>>-------------------------------
>>>>
>>>>
>>>>
>>>>>>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
>>>>>3. Normalize the tables, don't add fields which are seldom used.
>>>>>4. Reuse deleted records