Paradox Community
Search:

 Welcome |  What is Paradox |  Paradox Folk |  Paradox Solutions |
 Interactive Paradox |  Paradox Programming |  Internet/Intranet Development |
 Support Options |  Classified Ads |  Wish List |  Submissions 





Welcome to the Paradox Community Wish List - Page 8. To have your own wishes added to the list click here.


General
  • Correct internal values for Date/DateTime for dates prior to January 1, 0001. Paradox incorrectly treats all years in the B.C. era as leap years.
  • A command line option to load Paradox maximized.
  • Multi-threaded. Paradox would create its own category of application. Front end to Client/Server. Enterprise Level Database Driven Web Server (in conjunction with repaired OCX).
  • I find it would be nice to see the removal of the version specific, as it relates to delivered documents.

    I do not see why a document (form, report, script, library) which was compiled with no errors could not be read with a newer version of the program. Since Paradox is said to be backward compatible, why is it impossible to read a prior version of a delivered document?

    It would be very useful in (3) particular cases:

    (1) When different versions of Paradox are running at the same time, it would allow to deliver the documents with the lowest version and still be able to run the application.

    (2) When upgrading Paradox, it would be much simpler to upgrade the applications.

    (3) When using third-party tools it would be possible to continue using these tools without any problems. I am very reluctant to buy any 3rd party tools now, since the people who sell them, normally give a delivered version of the application. Unfortunately many of them are often out of business or not providing any upgrades after a period of time.

    I recently faced this issue with Woll2Woll - I have been using ezDialog and ezDoc since Paradox 7 but now that they do not support Paradox 9, it is a bit scary. It is not a problem with ezDialog but it is one with ezDoc.

    I have had tools from prior versions of Paradox 7, which I had to stop using because they were from small programming firms that no longer exist.
  • Inbuilt Planning Tools. I am surprised that there isn't some inbuilt means of planning / tracking what one is doing with our Paradox apps. Things such as:

    1. a taskflow scheme into which one could slot names of forms, reports, scripts, libraries etc as well as comments (problems, yet-to-do, mooted improvements etc), other called programs, network issues, hardware etc. This could be done elsewhere but by doing it here (i.e. within Paradox) it might serve to keep big picture issues in mind when buried in detail.

    2. Automatically generated control tables (I think that's the term?) i.e. tables of field names, table names etc for a given app, and the ability to more powerfully use that interactively.
  • Library use tracker ... be able to see a list of all the places where a given library is called. "Where" would mean object, event etc. Surely that would help encourage and simplify library use.

Page 1: Data Model Designer/Dialog and Design Mode Features
Page 2: Miscellaneous
Page 3: Object Additions/Improvements
Page 4: Object Explorer, ObjectPAL Editor and Debugging Tools
Page 5: ObjectPAL Language
Page 6: Printing and Reports and Project Viewer
Page 7: Tools/Experts/Interactive Features

Page 9: Suite Integration


Paradox Community Newsgroups


 Feedback |  Paradox Day |  Who Uses Paradox |  I Use Paradox |  Downloads 


 The information provided on this Web site is not in any way sponsored or endorsed by Corel Corporation.
 Paradox is a registered trademark of Corel Corporation.


 Modified: 15 May 2003
 Terms of Use / Legal Disclaimer


 Copyright © 2001- 2003 Paradox Community. All rights reserved. 
 Company and product names are trademarks or registered trademarks of their respective companies. 
 Authors hold the copyrights to their own works. Please contact the author of any article for details.