Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Visual Foxpro DB size
- Thread starter rpk2006
- Start date
crewchiefpro5
Programmer
2 gig per table. If you need larger then break it up into several tables.
Many security enhancements, go to the Microsoft web site to see all of them.
Many security enhancements, go to the Microsoft web site to see all of them.
alvechurchdata
Programmer
As crewchiefpro5 says it's 2 gig per table. If you're comparing with other products remember that a database can consist of many tables and a VFP app can have many databases open at once.
Look for "system capacities" in VFP Help for more details.
Geoff Franklin
Look for "system capacities" in VFP Help for more details.
Geoff Franklin
Mike Gagnon
Programmer
To be more precise, the limit is 2gigs per file, not just tables.
Mike Gagnon
If you want to get the best response to a question, please check out FAQ184-2483 first.
Mike Lewis
Programmer
Rpk2006,
As Mike Gagnon pointed out:
To be more precise, the limit is 2gigs per file, not just tables.
That's important, becuause if the table has one or more memo field, the memo text will be a separate file, which might easily be bigger than the table itslef.
__________________________________
Mike Lewis (Edinburgh, Scotland)
My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)
As Mike Gagnon pointed out:
To be more precise, the limit is 2gigs per file, not just tables.
That's important, becuause if the table has one or more memo field, the memo text will be a separate file, which might easily be bigger than the table itslef.
__________________________________
Mike Lewis (Edinburgh, Scotland)
My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)
- Thread starter
- #6
Mike,
I also want to know, how the VFP table gets loaded into memory. As is said about MS Access, it uses flat file system. So when the table is accessed, whole of the table gets loaded into memory. If the database becomes large enough and system requirements are not upto the mark, the performance of the application becomes sluggish.
Is it same with VFP?
I also want to know, how the VFP table gets loaded into memory. As is said about MS Access, it uses flat file system. So when the table is accessed, whole of the table gets loaded into memory. If the database becomes large enough and system requirements are not upto the mark, the performance of the application becomes sluggish.
Is it same with VFP?
Mike Lewis
Programmer
Rpk,
No, that's not the same with VFP. Essentially, VFP will only read the records that you request, although it does also use a form of buffering and caching to improve performance.
The amount of free memory will never limit the size of the table.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)
No, that's not the same with VFP. Essentially, VFP will only read the records that you request, although it does also use a form of buffering and caching to improve performance.
The amount of free memory will never limit the size of the table.
Mike
__________________________________
Mike Lewis (Edinburgh, Scotland)
My sites:
Visual FoxPro (www.ml-consult.demon.co.uk)
Crystal Reports (www.ml-crystal.com)
alvechurchdata
Programmer
Fox isn't like Access. An Access database stores all the records of all the tables and indexes in a single huge .Mdb file and startup can be very slow indeed as it loads this file. FoxPro stores its tables and indexes in separate files which makes it faster. When a properly-designed Fox system is asked to retrieve information it will load the index into memory then go to the correct offset within the data file and retrieve the record requested.
Fox does have the capacity to do without the index and load the entire table into memory for a brute-force search. This can be quicker for very small tables but it's the wrong technique for most tables.
By the way - don't worry about the phrase "flat file" - any relational database is a collection of flat files each of which holds information about one aspect of the system.
Geoff Franklin
- Status
