Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!sdd.hp.com!swrinde!ucsd!ucbvax!cis.ohio-state.edu!magnus.acs.ohio-state.edu!gburlile
From: gburlile@magnus.acs.ohio-state.edu (Greg Burlile)
Newsgroups: comp.databases
Subject: Re: Paradox 3.5 Record Size Calculation
Message-ID: <1991Jun13.144939.12627@magnus.acs.ohio-state.edu>
Date: 13 Jun 91 14:49:39 GMT
Article-I.D.: magnus.1991Jun13.144939.12627
Sender: news@magnus.acs.ohio-state.edu
Distribution: na
Organization: The Ohio State University
Lines: 15
Originator: gburlile@bottom.magnus.acs.ohio-state.edu
Nntp-Posting-Host: bottom.magnus.acs.ohio-state.edu

As a general rule you can use the following information to determine the number
of bytes per record:

 Field Type    Description       Bytes for Storage
 ==========    ===========       =================
     A         Alphanumeric      1 byte per character
     N         Numeric           8 bytes
     D         Date              4 bytes
     S         Short Number      2 bytes
     $         Currency(Numeric) 8 bytes

The above values can be used to calculate the number of bytes per record.
usually there are some sort of database "overhead" storage of about 1300 bytes.
This should help get you in the ball park for users to be able to estimate disk
storage needed.