>Hi all
>
>Been a while since I posted on here, hope everyone is keeping well.
>
>I'm writing an app and due to the large amounts of data it's going to be storing I need to be careful about the 2Gb table limit.
>
>2 questions really:
>
>a) Is it possible to project table-size, if I have a table with say, 4 columns, would I be able to get a "rough" idea of how many records it will populate without reaching the limit?
>
>b) Secondly, I want to ensure that the 2Gb limit won't be reached, what's the best way to ensure it doesn't reach it? If there is an answer to question a then I'll keep an eye on the record count, however if this is not possible I'll need some other mecahanism.
>
>Thanks
>Kev

a) Even if that table has 0 records in it now you can calculate "how many records will fit in X bytes". Roughly calculation is:

lnTargetBytes = 2*1024*1024*1024
? int((m.lntargetbytes-HEADER())/RECSIZE())

If table has no memo/general/BLOB type fields thjis would give you your limits.

b) You can keep an eye on reccount() then or directly on file size itself.

PS: Such a case sounds to be a great candidate for SQL server (or some other backend).
Cetin