Very Computer

What is the opinion regarding converting from Paradox 3.0 for DOS to Access
rather than Paradox for windows?  Which is most cost effective, less time
involved?  Our existing database was set up by a predecessor- which means many
of the scripts written needs to be translated.

Quote:> What is the opinion regarding converting from Paradox 3.0 for DOS to
> Access rather than Paradox for windows?  Which is most cost effective,
> less time involved?  Our existing database was set up by a
> predecessor- which means many of the scripts written needs to be
> translated.

As both involves practically a complete rewrite from scratch, the
difference mainly depends on the amount of onsite expertise you have. If
you have more Access expertise, go with Access. Otherwise, stick with
Paradox.

--
Kuo-Sheng "Kasey" Chang / spam-hater /
Paradox guru / X-Com Guru / Sci-Fi Fan /
Treknologist / Military buff / a guy (yes, male!)

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

if you have no pre-existing knowledge of either current product, the most
important issue is finding thee right competent pregrammer to do the work for
you.. assuming your app is failly small and simple, either product will work..
it's the programmer that's important.. the current code is merely a guideline, for
many reasons.. it hopefully is the map to your business rules..

--
Steve Green
Corel CTech - Paradox
Diamond Software Group, Inc.
Waldorf, Maryland  USA

http://www.diamondsg.com

Given all other things are equal, staying with Paradox will allow you
to retain your current tables during the period of development and
deployment of the new version. This may be of considerable one-time
benefit, if you have a lot of data involved and the programs you are
using now can be relied on while development proceeds. You also tend to
simplify arguments over which version is "right" when both sides use
the same tables.
--
Mike Irwin                    It's not because things are hard that we
[Volunteer CTech Sysop,       don't dare them; it's because we don't
not a Corel employee]         dare them that they are hard - Seneca.

I would convert the system to Paradox for Windows, without question.

Having done many, many conversions of this kind in years past, I can
also say that you will find that much of the old Paradox for DOS code
will not need to be converted, and that much more of it will be vastly
simplified by the enhanced capabilities of Paradox for Windows.

As for Access, frankly I am becoming more and more dissatisfied with it,
each release.  "And I don't give a <!> who sells it!"  :-)  Our business
consists of "Paradox, Access, and Delphi" (and ChimneySweep ;-)) ... and
Access is not putting on a good show these days, while Paradox keeps
chugging along.