Q: Paradox limitations.
Brede Bergseth Aaker
I wonder if someone could tell me the limitations in paradox.
Example: Maximum numbers of records in an table and so on...
One of my tables will in one year grow with about 9 000 - 18 000
record pr year.
Need some advice!
regards
Brede
Paul Ferrara
using dBase instead of Paradox.
Paul / ColumbuSoft
www.columbusoft.com
Brede Bergseth Aaker <br...@nospam.lesja-data.no> wrote in message
news:3923B2BA...@nospam.lesja-data.no...
Sanford Aranoff
Please explain your reasons.
Sundial Services
thread that dBase tables are "necessarily better." In fact, all things
considered, between the two choices I -dis-agree...)
A Paradox table contains up to 65,535 physical blocks, each one a
multiple of 2K in size, each one containing an integral number of
records (less 6 bytes slack per block). Records do not span blocks.
This will enable you to do the math.
Tables that grow a few ten-thousand records per year are not a challenge
to Paradox and are not unusual.
>Brede Bergseth Aaker wrote:
>
> Hi
>
> I wonder if someone could tell me the limitations in paradox.
> Example: Maximum numbers of records in an table and so on...
>
> One of my tables will in one year grow with about 9 000 - 18 000
> record pr year.
>
--
------------------------------------------------------------------
Sundial Services :: Scottsdale, AZ (USA) :: (480) 946-8259
mailto:in...@sundialservices.com (PGP public key available.)
> Fast(!), automatic table-repair with two clicks of the mouse!
> ChimneySweep(R): "Click click, it's fixed!" {tm}
> http://www.sundialservices.com/products/chimneysweep
Jean-Pierre Martel
> You are the first person to say this. Everyone else recommends Paradox.
> Please explain your reasons.
>
dbf tables and this format is the native format for many database
softwares (dBASE of course, Clipper, FoxPro, Lotus Approach, AlphaFour,
etc.).
In 16 years of use, I never had corruption on a DBF table (note: I don't
want to suggest that it is the case with Paradox - I don't know): my
point is that DBF is a solid standard, recognized by more softwares than
Paradox (that is one of the rare good points of getting old: more people
know us).
Jean-Pierre Martel, editor
The dBASE Developers Bulletin
http://www.tnm.de/dbulletin/bulletin.htm
Paul Ferrara
messages containing good reasons not to use them.
The number of people having problems with dBase tables is many orders of
magnitude fewer. Not to mention the points that Jean-Pierre made.
Paul / ColumbuSoft
www.columbusoft.com
Sanford Aranoff <SAra...@nusinc.com> wrote in message
news:3923F8C9...@nusinc.com...
> You are the first person to say this. Everyone else recommends Paradox.
> Please explain your reasons.
>
> Paul Ferrara wrote:
> >
> > If you haven't yet decided on which tables to use, I'd strongly suggest
> > using dBase instead of Paradox.
> >
> > Paul / ColumbuSoft
> > www.columbusoft.com
> >
> > Brede Bergseth Aaker <br...@nospam.lesja-data.no> wrote in message
> > news:3923B2BA...@nospam.lesja-data.no...
> > > Hi
> > >
> > > I wonder if someone could tell me the limitations in paradox.
> > > Example: Maximum numbers of records in an table and so on...
> > >
> > > One of my tables will in one year grow with about 9 000 - 18 000
> > > record pr year.
> > >
Phil Oneacre
handled successfully. Pdox has good points and bad points but I prefer it
over dbase. Now days I have moved away from the BDE and am using DBISam a
lot.
Bill Todd (TeamB)
General BDE Limitations
48 Clients in system
32 Sessions per client (3.5 and earlier, 16 Bit, 32 Bit)
256 Session per client (4.0, 32 Bit)
32 Open databases per session (3.5 and earlier, 16 Bit, 32 Bit)
2048 Open databases per session (4.0, 32 Bit)
32 Loaded drivers
64 Sessions in system (3.5 and earlier, 16 Bit, 32 Bit)
12288 Sessions in system (4.0, 32 Bit)
4000 Cursors per session
16 Entries in error stack
8 Table types per driver
16 Field types per driver
8 Index types per driver
48K Size of configuration (IDAPI.CFG) file
64K Max size of SQL statement (RequestLive=False)
4K Max size of SQL statement (RequestLive=True)
6K Max size of SQL statement (RequestLive=True) (NEW BDE 4.01)
16K Record buffer size (SQL and ODBC)
31 Table and field name size in characters
64 Stored procedure name size in characters
16 Fields in key
3 File extension size in characters
260 Table name length in characters (some servers might have other
limits)
260 Path and file name length in characters
Paradox Limitations
127 Tables open per system
254 Tables open per system (NEW BDE 4.01)
64 Record locks on one table (16Bit) per session
255 Record locks on one table (32Bit) per session
255 Records in transactions on a table (32 Bit)
512 Open physical files (DB, PX, MB, X??, Y??, VAL, TV)
1024 Open physical files (DB, PX, MB, X??, Y??, VAL, TV) (NEW BDE 4.01)
300 Users in one PDOXUSRS.NET file
255 Number of fields per table
255 Size of character fields
2 Billion records in a table
2 Billion bytes in .DB (Table) file
10800 Bytes per record for indexed tables
32750 Bytes per record for non-indexed tables
127 Number of secondary indexes per table
16 Number of fields in an index
255 Concurrent users per table
256 Megabytes of data per BLOb field
100 Passwords per session
15 Password length
63 Passwords per table
159 Fields with validity checks (32 Bit)
63 Fields with validity checks (16 Bit)
dBASE Limitations
256 Open dBASE tables per system (16 Bit)
350 Open dBASE tables per system (BDE 3.0 - 4.0, 32 Bit)
512 Open dBASE tables per system (BDE 4.01, 32 Bit) (NEW BDE 4.01)
100 Record locks on one dBASE table (16 and 32 Bit)
100 Records in transactions on a dBASE table (32 Bit)
1 Billion records in a table
2 Billion bytes in .DBF (Table) file
4000 Size in bytes per record (dBASE 4)
32767 Size in bytes per record (dBASE for Windows)
255 Number of fields per table (dBASE 4)
1024 Number of fields per table (dBASE for Windows)
47 Number of index tags per .MDX file
254 Size of character fields
10 Open master indexes (.MDX) per table
220 Key expression length in characters
--
Bill Todd (TeamB)
(Questions received via email cannot be answered.)
Brian Bushay TeamB
>I wonder if someone could tell me the limitations in paradox.
>Example: Maximum numbers of records in an table and so on...
>
>One of my tables will in one year grow with about 9 000 - 18 000
>record pr year.
Paradox tables use a fixed block size. The maximum table size depends on what
the block size is set to. Block sizes can be 1,2,4,8,16 and 32K
Maximum table size is calculated at 64 megs per K of block size.
The maximum records that can be stored depends on how many records can fit in a
block.
for other limts see http://community.borland.com/article/0,1410,15159,00.html
--
Brian Bushay (TeamB)
Bbu...@NMPLS.com