Hello to the group.

We are currently using a legacy app which runs Paradox 4.5 (?). I know
it launches Paradox Runtime 4.5 when the program starts. While it is
still working, its use has been problematic at best on any system
beyond Windows 98. The app was developed internally in 1995, and to my
knowledge, has had no support or modifications since then, other than
maybe when it stops working. To my knowledge, we have been inputting
data, most likely lots of data, since 1995.

As I have no experience with Paradox, in the opinion of the group, are
we headed down a path of eventual total failure of this app. Could we
eventually reach a point of too much data?

As of 6/17/04 our largest company had over 200,000 records in database
1 and 1.5 million in database 2. We have data for 64 companies in
each database.

It is my opinion that we need a complete ground up redevelopment of the
entire app; however, management feels we can continue to coast on what
we're using, unless I can make a strong case otherwise.

Any advice is greatly appreciated.

Thanks.


Michael

Michael:

I don't think your situation sounds all that grim, but it's hard to say from
here.

Paradox for DOS or Paradox for Windows?

If you are using Paradox for DOS 4.5, it should run in WinXP, but will
probably have problems under Windows2000.
If you are using Paradox for Windows 4.5, most of your problems should go
away if you migrate to a Win32 version of Paradox (e.g., 7-11).

If you have immediate plans to go to Windows Vista ASAP, early reports are
that both DOS and Windows versions seem to work, but there's no guarantee.

Max table size for the Paradox table format is 2GB. Practical size is
usually smaller (how much smaller depends on the apps using it), and you
will encounter index problems at 1/2 this size.

Are there any major new features you need in the current application?

Do you have the money laying around to build a replacement?

Find someone who knows Paradox to come in and give you an assessment of how
critical your situation is. The future isn't terribly bright for Paradox,
but Paradox apps should continue to work for the forseeable future. Your
biggest risk right now is not that you are using a dying product but rather
that you have no one to support it who is knowledgeable in that product.

--
Larry DiGiovanni
Digico, Inc.
IT Consulting and Staffing Solutions
www.digicoinc.com
Check out www.thedbcommunity.com for Paradox resources.

Larry,

Thanks for the response. I believe that it is Paradox for DOS, as when
I launch the app, it opens a DOS window where it says Paradox Runtime
4.5, then it displays a menu where I can select what to do. After that
selection, there is a very crude windows interface for importing data
and running reports.

The two primary users of this app, have been migrated to XP machines in
the last six months, so they will not be migrating to Vista anytime
soon.

While the app is working, it doesn't seem stable, and it took some
fiddling to just get it working under XP. It will work fine for a
while, then will just stop running reports (I believe reports are
generated with Crystal Reports). If they exit the app, and restart it,
they will be able to run one report, then exit again. This cycle will
continue for a while, then it will start working again fine. Also, if
they hit an invalid key sequence, occassionally, instead of beeping
once, it will beep continuously and lock up the app, requiring a hard
termination of the app.

We have had money in the budget since 2004 to have the app redeveloped,
but as yet, have not been successful at finding anyone locally who
could do the work. We are at the point where there is a new things
that need to be added to the database and the reports, due to the
changing nature of the source data. I am concerned that simply
upgrading Paradox and Crystal Reports, will not be enough without
upgrade the front end interface.


Michael

Michael,

This is not a "normal" issue with Paradox. Sounds more like a Crystal
problem. However, some printing issues do arise with Paradox, but nothing
major. I've penned a few notes on such issues (and on many others!!) at
http://www.kennedysoftware.ie/oldapps.htm, which might help. (Many sections
in there are "heavy", so get a Coffee first!).

The above link has some notes on BEEP/SLEEP problems/solutions.

- Mike

Bruno wrote:

1. Local to where?
2. Have you considered using resources that are not local?

First thing you gotta do is get an idea what it would cost to fix bugs
and/or make the enhancements. Then compare that against the cost of a
replacement system. It would be well worth your while to bring someone in,
even if you have to fly them in from out of town for a few days, to help you
get a handle on your system.

--
Larry DiGiovanni
Digico, Inc.
IT Consulting and Staffing Solutions
www.digicoinc.com
Check out www.thedbcommunity.com for Paradox resources.

I don't agree. This case might just be an example of how "old" software can
be perfectly OK for a very long time at very low cost. How much would two
upgrades have cost? Had it been worth it?

Maybe it's time to upgrade today, maybe it can run for another 10 years?
Without knowing the app and the tasks it has to fullfill it's impossible to
tell.

Anders

Anders,

??

Perhaps I should have added - "and you didn't spend a small fortune so far
on unnecessary re-writes, and the sky has not fallen..."

Absolutely!! That's what I had intended to convey! My apologies for not
doing so.

....and without knowing the expected requirements over the long-term... eg,
email interfaces, website integration, integration with some "office"
products, larger databases (C/S), etc...

Agreed also. There's too much pressure to "upgrade/rewrite", with
Benefit/Costs < 1.00.

- Mike

Mike,

No need to apolgize, it was probably me that didn't read your post carefully
enough.

Seems like we have exactly the same view about this!

Best regards

Anders

Bruno wrote:

sorry for the late reply.. long day, but the others have given you some of
the answers you need..


download 4xguide.zip from my web site.. many of your comments (in both
messages) indicate that the installation and/or command line switches are
wrong.. that'll fix many of your immediate problems.. PdoxDOS runs fine on
everything except Win2000..


lack of knowledgable support, and lack of regular maintenance, will
eventually lead to a short-term failure.. happens *every* time.. but it
rarely turns into a permanent disaster.. take a look at my Sanity Check
page, too.. you're a prime candidate..


sure.. but there are ways to get around that.. PdoxDOS tables can be up to
256 meg each, and are smooth over 100 meg.. how big are your tables?


here's your case.. there are only a handful of experienced PdoxDOS
developers left on the whole planet.. to be blunt, that means there's no
guarantee of intelligent support.. you don't know how the app works, and
nobody else in-house knows.. if your company doesn't have a replacement
strategy ALREADY IN PLACE, they're fools..


--
Steven Green - Waldorf Maryland USA

Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales - Corel CTech Paradox
---------------------------------------------------
Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Trading Cards and other Sports Memorabilia
---------------------------------------------------

Wow. I wish I'd found this group a year ago. I think that ya'll have
provided the best information I've ever been able to find. I'll check
out all the links later.

We are located in Colorado Springs, CO. To date, we have had two
quotes to redevelop the app. I believe they both involved migrating
the data to SQL with an HTML or Access front end. Neither quote has
been acted on. I believe the interest in having someone local do the
development is so that ongoing support would be easier to access.

I think that management has felt safe with the casual contact they have
had with the former employee who actually did the development of the
app. However, that contact has become less frequent over the years.

As it seems to be the popular opinion here that redevelopment is may
not be necessary, but an evaluation by a Paradox Pro would be a great
idea, I'll run it past management, as the whole issue of this app has
taken some precedence lately.

Steven, when you ask for table sizes, do you mean the size of the .DB
files?


Michael