Paradox Vs Access


i need to write an application
what is the right choice Access or Paradox ?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

well there is no "right choice" it is what you know best probably.

there is no doubt more delphi support for paradox but alot of perple are now using access also.

It depends largely on what your application is designed to do. For large multi-terminal, multiuser client server applications,  you would want to use Paradox(or Oracle,FoxPro... just about ANYTHING but Access). In contrast, if you are developing a small single user type application, then Access makes sense. The reasons for this are varied, but primarily, Access stores it's tables in a single MDB file. This means that if you are querying acros several tables at a time, the cursor has to literally junmp all over the MDB file to etrieve the required dataset.And of course there is , as  Inthe mentioned, the fact Delphi lends itself very easily to Paradox where Access is  more work through ODBC drivers, etc. In short, it is a question not so much or "good" or "Bad", but rather "What makes sense for this project".

Good luck!!  
in fact, these stuffs are both desktop-level database system, so if you really want a client/server application, you should use mssql/oracle stuff instead.

As far as I see, if you use paradox, you should use bde, and if you use access, dao or ado should be used.

and, I think access is better than paradox for both single user and muilti-user enverioment.

Paradox is slower and unsafer.
Paradox is slower than access and foxpro, even slower than dbase.

and, when a power lose or other accident accor, the table should corrupt.

so I strongly recommanded you use Delphi 5's ADO components and Microsoft Access to make your program.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

hi chengjian

>Paradox is slower and unsafer.
>Paradox is slower than access and foxpro, even slower than dbase.

thats not true

>and, when a power lose or other accident accor, the table should corrupt.

that happens to all databasesystems, also to sql-serversystems

>I strongly recommanded you use Delphi 5's ADO components
> and Microsoft Access to make your program

this may your subjective choice

my subjective choice
-paradox is even better and faster than access
-paradox is on sql-side better than access, because standard sql is used (access -> jet sql -> proparitary)
-is there a crash, in paradox is one file corrupt -> access the whole mdb-file
-i use paradox in some applications since ~10 years without any problem in multiuser-enviroments with 10000s of records and more than 100 tables

therefore asi
decide on where the datas are also used, should you want to share the data with other m$-office-products then decide to access (thats the only argument for me to use access)

remark :
ado is trendy,
native is the best

Amen to everything meikl said. Access is notoriously sluggish and the idea that anyone in their right mind would even consider it for anything other than small applications is ludicrous. I'd be laughed out of my office if I were suggest that we migrate our database from SqlServer to Access. Access is "Database for Dummies". Not that it doesn't have its place (see my comments above), but to suggest that it is preferable to Oracle is absurd!
I prefere to use Paradox because it is a native BDE format. You can easily access Paradox tables, create new tables at run time, and you can easily deploy applications that use Paradox tables.

See this Borland documentation page to see Paradox limitation:

If you want to use Access databases I advice you either to use MS-Access or Visual Basic, but if you are Delphi programmer it is better to use Paradox
asiAuthor Commented:
now , how do i need to give the points , ha ?
Well, you offer 16 points and got about as many responses, tough call.... <G>

another suggestion use filemaker pro ;-)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.