files over 2 gig

[murrayl]

What are the limitations on foxpro 2.5b for DOS for dbf file size and number of records? I have a database which is quickly approaching the 2 gig limit I've seen mentioned here. What will happen when the limit is reached?

 

[fluteplr]

When you say database do you mean a single DBF? If so it will stop working. You will not be able to add anymore records. Your choices are to archive off some of the data, split it into two tables 'vertically' each one with some of the fields and a field that links the two tables or split the table horizontally (put some of the records, like the old ones, into one table and the others into another table. You will obviously have to do some modifications to your table with the last two options.

If the problem is an FPT file getting that big, have you run a pack memo lately? Also if you have deleted records and have not packed the table you might try that to see how much space you get back.

Also if I have not made it clear the 2 gig limit is per individual file dbf, fpt or cdx not for the files added together.

 

[zimbaliza]

Just tried under Foxpro 2.6a for windows...

have managed to get the dbf to 2 gigs.... with an
index, after that.... Fox Die's.....

haven't got any dos partitions > 2 gigs, to test
how fpd will handle it, but I think it would be the
same, fox will just stop.

I would archive the data, or split over multiable
DBF's.....

should speed up *ALOT* with smaller tables

(our fox tables hang around 1.4 gigs-1.6 gigs about 12-14 million records, we archive to 2 years sales), use FPD, FPW 2.6.....

Zim

 

[riss]

Is there any limitation on the size of a directory all together? Has anyone seen corruptive behavior in data files which are at least 1/2 gig for a single dbf?

 

[fluteplr]

not related to the file size. There is a speed issue if you get more than 2000 files in a single directory. I have not seen corruption related to file size, it is almost always related to network problems and/or a failing hard drive.