Versions des environnements
>I don't think so. Your apps just will need to be redeployed with the new Runtime to access tables bigger than 2Gb.
>
Samuel,
from your company site:
# Table size limit of 16 Exabytes. The engine is 64 bits capable, so the maximum table size is 264 - 1. This is nearly 4,000,000,000 times bigger than the actual limit.
# More than 255 fields by table.
I interpret this as table size in bytes and number of fields. What I miss is a statement on the maximum number of records in the enhanced tables: vfp's limit of 1 billion is in reality cut down by the 2 Gig border to something on the order of 10 to 50 million records and sometimes I need to vertically split tables to reach even that number - which is one of my worst gripes with vfp.
Having nearly unlimited table size would help a lot since all vertical splits would be unneccessary, but if the RecCount() is still limited to something from the 4-byte world (2**32 or 1 billion positve numbers...) actual table sizes from typical business apps will probably never reach those limits (even when saving bitmapped documents - you would need movie sizes <bg>). But the border on "usable reccount()" would only be raised 50 to 200 times - which would help me for instance tremendously in my current gig (datamining) but can be problematic with small sized transaction or measuring data.
Using 8-byte record pointers probably needs a much larger effort (new cdx format, different header) than just rasing the 2 Gig table size limit - any statements to that topic ? Don't get me wrong, for *me* just raising the usable Reccount() 50 times alone would make a purchase / upgrade at typical vfp cost a no-brainer if it was a vfp update.
The big questions for are:
1) the stability of the new system - we are well aware of vfp's warts, but it *is* a very stable product where I don't have to verify every result.
2) how code compatible is the new system ? Learning the slight differences is another type of cost - in the same league as the cost of splitting tables. These costs are less visible than a purchase price, but can be markedly larger...
regards
thomas
Précédent
Suivant
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement