As both involves practically a complete rewrite from scratch, theQuote:> 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
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.
Corel CTech - Paradox
Diamond Software Group, Inc.
Waldorf, Maryland USA
> 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.
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
Ok, I'm reposting this again in one last cry for help. If anyone has
ANY suggestions, please respond.
Can anyone help me to either find or write a routine which duplicates
the "MultiAdd" routine found in Paradox DOS? I've never used the
routine, and don't know exactly what it should be doing. I need to
duplicate it for a conversion that I'm doing.
Someone please help