I have to develop e new application.

Somebody can give me informations about
Paradox tables Vs MDB files (Access)?

Thanks in advance
Luca

What information do you want?  Delphi provides better support for
Paradox tables than it does for Access files.

Bill

(Sorry but TeamB cannot answer support questions received via email.)
(To send me email for any other reason remove .nospam from my address.)

Hello Bill,

Im a serious Delphi programmer right from the start but i dont
understand something. I hope you can help.

Im currently using an app. on a novell network with 12 Paradox 7.0
tables with a mean of 12.000 records each. My problem is opening the
tables (also stand alone), they are opening far to slow, i'm talking
about getting at least 2 coffees. Searching seems ok, but a join over 4
tables ..really.. you can do lunch! so im experimenting with Access 97
tables and it the result are tremendous (too tremendous i think)

for example the join: if Access(in D3.0) is factor 1 than paradox is
factor 5.4 that means a Access join of 15 secs translates  to a 15*5.4
is over 80 secs.

the results of the join in MS Access '97 office is about the same as in
Delhi 3.0

greetings Edward.

to work around

My experience is that Jet 3.5 kicks butt, in part because it does not pull
down records into the local cache, it pulls down indexes only, indexes are
on separate pages, and only then does it fetch the matching records
selectively. It then normally uses an async lazy writeback technique to
sync the local cache with the actual MDB file, though you can force sync
writes if you want. The whole replication technology in Access is
apparently how the cache magic happens. All in all Jet is way better
optimized than any of the older file-based databases. The new FoxPro5
apparently works like that too. If you skip BDE and go directly to the DAO
object layer, e.g. in VB5, the performance difference is even bigger, I'm
seeing 50/1 differences between a Delphi Query and a VB query on the same
database. I'm having a hard time making Delphi even come close. In theory
one should be able to bypass BDE and talk to the same COM layer VB talks
to, but no matter how you cut it, Jet seems way more tweaked than Paradox.

Fernand

ed <eSp...@freemail.nl> wrote in article <34C6371E.7...@freemail.nl>...

I have no idea why it should take a long time to open tables on a
Novell network.  I have not had that problem.  I assume that the delay
is at the OS level which explains why Access is faster since it only
has a single file to open. The difference in the joins, I suspect, is
twofold. First the optimizer for local tables in the BDE is not always
very smart about using indexes and second the BDE fetches the result
set.

Bill

(Sorry but TeamB cannot answer support questions received via email.)
(To send me email for any other reason remove .nospam from my address.)

--
Brian Bushay (TeamB)
Bbus...@DataGuidance.com

The lockdelay changing wil not affect the standalone-performance. The
only way i can think of to improve performance Big time is to convert
the tables to Access97 format.

greetings and already thanx