FH> Does someone has ever succeeded in building an application with
 FH> Paradox For Windows 4.5 under WFW 3.11 that has fully satisfied his
 FH> client ? I mean no lock up, no strange behavior, no crash for a
 FH> reasonable period of time.
I have over a dozen apps written for different clients that work just fine. I 
have used Vers 1.0, 4.5, & 5.0. One thing you may want to look at is how much 
memory your apps require. I originally found that my apps were wasteful of 
RAM and caused problems like you describe. I found that a minimum of 10MBs 
and careful planning (not too many tables open at the same time) fixed the 
problem. Also I found that some problems were caused by users opening too 
many apps at one time. I now check for resources to make sure there are 
enough to support the apps I write.  FH> In fact, as I understand that 
Paradox for DOS has many problems
 FH> as well, I am wondering if the Borland DataBase Engine itself is not
 FH> the culprit. In this case, Borland C++ 4.5 + DataBase Engine and
 FH> Delphi would also fail.
I have found the DOS ver 4.0 to be very stable even on networks. Again you 
need to be very careful about how you use RAM. You should check and make sure 
you clear all variables and tables when you are finished working with them. 
As far as Delphi is concerned I am working on my first network app in it 
right now so I can't say for sure what problems I may encounter. From 
experience though I figure the same will be true of Delphi as Paradox.
 FH> So, do you believe that one can develop rock-solid applications
 FH> with Borland software ?
Absolutely. I have developed more than 40 apps with various versions of 
Paradox and have more than 40 satisfied customers. I have tried Dbase, 
FoxPro, & Access and have found Paradox to be far superior to the others. 
Well thats my 2 cents anyway.
Terry
---
---------------