DBExpert

Version: 
2.0.9
Release date: 
Sunday, 25 February, 2018
Price: 
US$ 119.00

License:

Interface:

DBExpert is an application builder with a relational database manager built into it.

DBExpert is fully object-oriented in its design and interface. It gives you all the advantages of rapid database application development through the integrated use of Tables, Forms, Reports, Queries, and Macros.

Even when starting from scratch, creating a database is as easy as filling in forms which describe the fields of your tables. There's no data definition language to learn.

Need to make a change? No problem. Just add or change the information on the design forms and DBExpert automatically changes the database definition and migrates your data.

Have existing data? DBExpert works seamlessly with DB2, dBASE, Clipper, FoxPro, and Oracle databases -- standalone or simultaneously with other applications. DBExpert can also import most forms of fixed format and delimited ASCII data files.

With the Power of SQL & REXX

There's real power behind the interface. The queries you create in DBExpert's query designer are internally translated in SQL for access to the database. You can view and even edit the SQL right in the query designer - and changes you make are reflected in the point-and-click interface.

For more demanding situations, you can use macros to process your data. And DBExpert's macro language isn't some wimpy afterthought - it's REXX. These macros can be run directly or linked to form-based events such as 'next field', 'next record', or 'before database update.

To really bring things together, you can even call your REXX macros from inside SQL queries. No other product gives you this powerful combination.

DBExpert also includes dozens of functions that extend REXX to provide access to your DBExpert tables, queries, forms, and reports.

In addition to all of the power of SQL, REXX, and point and click, DBExpert supports a variety of database systems and formats. Instead of using some proprietary database format, DBExpert uses the database format you prefer. DBExpert can even use multiple databases in the same form, query, and report -- letting you combine information from a variety of sources.

Converting data from one format to another is virtually automatic. DBExpert handles all of the technical differences between each database format to prevent data loss. You can even mix database formats in a single DBExpert application.

On the other hand, if simpler is what you want, DBExpert does that, too. It is the only fully-featured relational database system for OS/2 that can be used without programming or SQL.

DBExpert Supports These Database Formats:

  • dBASE III
  • dBASE IV
  • Clipper
  • FoxPro
  • FoxBASE
  • DB2 for OS/2 (UDB as well as earlier versions)
  • DB2 on other platforms (via UDB, DB2 Connect, or DDCS/2)
  • Oracle 7 for OS/2

DBExpert also includes extensive support for importing fixed-format or delimited ASCII files.

System Requirements:

DBExpert has the same system requirements as for OS/2 plus 5 Mbytes of disk space. It runs on OS/2 2.0 or higher (including OS/2 Warp, Warp Connect, and Warp Server). DBExpert is Warp 4 compatible and network Ready!

No additional software is required to use dBASE III, dBASE IV, Clipper, FoxPro, or FoxBASE tables with DBExpert.

To use DB2 tables with DBExpert (locally or on a DB2 UDB server), an appropriate version of DB2 for OS/2 or the DB2 Client Application Enabler must be installed. Access to DB2 tables some other platforms (such DB2 for MVS/ESA, DB2 for OS/400, and DB2 for VSE & VM, formerly SQL/DS) also requires DB2 Connect (or an earlier version of DDCS/2, as appropriate).

To use Oracle tables with DBExpert, Oracle 7 for OS/2 must be installed.

This software is distributed as compressed package. You have to download and manually install it; if prerequisites are required, you will have to manually install them too.

Manual installation

Available both as ZIP and floppy disk package:

  • download the ZIP package to temporary directory and unpack it to destination folder;
  • the floppy disk package is self-installing.

See below for download link(s).

Online documentation:

Following ones are the download links for manual installation:

Dbexpert sys3175 reduce error (25/2/2018, Roberto Gainza) Readme/What's new
Application name: cpul2-1.cmd What it does ?, It serves to reduce SYS3175 errors of Dbexpert, and perhaps other applications with a similar problem. That results in the unexpected closure of the application. How does it work: Read the cpu, with the program cpu.exe that is in Arca50 or higher. Calculate a percentage of use of the CPU, and find the most appropriate time to launch the desired program. Because of this, it does not repair anything and does not modify anything. It also does not guarantee 100% reliability in the target, but it reduces errors by approximately 90 to 95% o more. *In cpul2-1 this is 99% free of error. What do you need to use it: Arca50, or have the pcu.exe program installed. I have not tried it on ecs. Can not run on 4os2 only on os2 comman com How to use it in the Dbexpert: 1- Create a macro with the name you want. Similar to Mcpul2. 2- Make a copy paste of the text of cpul2.cmd, and put it in new macro, save. 3- Make a call to this macro, from any other macro in the dbexpert, just before the problematic process. Similar to: rc = dbeopen ('macro', 'mcpul2') Improvable things: Read the number of installed processors, and calculate the average with more values. And others.... Author: Roberto Gainza
 hobbes.nmsu.edu/download/pub/incoming/cpul2-1.zip
Ver. 2.0.9 (Runtime update) v. 2.0.9 (7/8/2000) Readme/What's new
DBExpert(tm) Relational Database for OS/2 from Sundial Systems List of Problem Fixes (FIXLIST.TXT) August 2000 This file contains a brief listing of each problem which has been fixed in DBExpert since the release of Version 2.0. The following problems were fixed in DBExpert version 2.0.9: * Executing large numbers of UPDATE (or INSERT) queries (possibly indirectly through other queries) gradually slows down query execution speed and eventually causes random failures, erroneous error messages, and possibly program lockup * Printing or previewing when a default printer is needed and no default printer is found displays a confusing error message * Import or export requests stop processing records if the main application window is minimized or hidden * Title bar of Preview window shows report name rather than report title * If an error occurs while running a macro on application startup, there is no obvious way to keep the application open * If the table names or totals options in the query designer are toggled on or off while some column attributes are being edited or selected, completing the entry or selection operation displays an erroneous error message * If a query is set to sort on other than the first column, that column becomes the first column once the query is saved and the query designer is closed * Reports with page footers which contain MLE fields which can grow, and which do grow to overlap past the bottom on the page, do not properly continue printing after the remainder of the footer is printed on the next page * Report detail sections which are set to "keep together" but which grow larger than the available page size never print * Query designer doesn't properly handle column inserts when multiple copies of the same table or query are used as sources in a single query * Queries involving conditions on identical column names from different tables may not properly associate the conditions with the correct table * Modifying column name of a table prevents any query that involves a join operation on that column from being opened in the query designer * MLE controls on forms do not visually refresh when their value is changed using dbeSetValue() * Alt+letter keyboard shortcuts do not work in the main portions of forms that contain a header and footer * Some report formatting options are not properly reset after a header or footer is removed from a report * Export improperly also lists INSERT, UPDATE, DELETE, and MAKE TABLE queries as possible sources (rather than only tables and SELECT queries) * dbeInt() returns incorrect value for 0 or any negative whole number * dbeSubStr() incorrectly uses 1, rather than the maximum value, for the count parameter if the count is not specified * dbeRunApp() does not correctly handle running of .CMD files * dbeChr() returns incorrect value if called in a macro * ASCII 'ff' (decimal 256) characters in imported data cause random problems during import and when viewing/using resulting table rows * Length attribute of report fields is ignored when displaying data on reports * Vertically scrolled windows in the query designer sometimes cannot be scrolled back into position after closing and reopening the design * Table window positions in the query designer are not always properly restored after closing and reopening the design * Some very long expressions and conditions in the query designer are truncated after closing and reopening the design * Update queries which involve join operations sometimes update the incorrect rows of the underlying tables * Some update queries which involve a join and an update on the "read only side" of a 1-to-N join would appear to execute rather than display the appropriate error message * Attempting to create a new application when OS/2 Warp FixPak 11 is installed sometimes causes and erroneous error and then application can't be created
 www.os2site.com/sw/apps/database/dbup209r.zip
Ver. 2.0.9 (Update) v. 2.0.9 (7/8/2000) Readme/What's new
DBExpert(tm) Relational Database for OS/2 from Sundial Systems List of Problem Fixes (FIXLIST.TXT) August 2000 This file contains a brief listing of each problem which has been fixed in DBExpert since the release of Version 2.0. The following problems were fixed in DBExpert version 2.0.9: * Executing large numbers of UPDATE (or INSERT) queries (possibly indirectly through other queries) gradually slows down query execution speed and eventually causes random failures, erroneous error messages, and possibly program lockup * Printing or previewing when a default printer is needed and no default printer is found displays a confusing error message * Import or export requests stop processing records if the main application window is minimized or hidden * Title bar of Preview window shows report name rather than report title * If an error occurs while running a macro on application startup, there is no obvious way to keep the application open * If the table names or totals options in the query designer are toggled on or off while some column attributes are being edited or selected, completing the entry or selection operation displays an erroneous error message * If a query is set to sort on other than the first column, that column becomes the first column once the query is saved and the query designer is closed * Reports with page footers which contain MLE fields which can grow, and which do grow to overlap past the bottom on the page, do not properly continue printing after the remainder of the footer is printed on the next page * Report detail sections which are set to "keep together" but which grow larger than the available page size never print * Query designer doesn't properly handle column inserts when multiple copies of the same table or query are used as sources in a single query * Queries involving conditions on identical column names from different tables may not properly associate the conditions with the correct table * Modifying column name of a table prevents any query that involves a join operation on that column from being opened in the query designer * MLE controls on forms do not visually refresh when their value is changed using dbeSetValue() * Alt+letter keyboard shortcuts do not work in the main portions of forms that contain a header and footer * Some report formatting options are not properly reset after a header or footer is removed from a report * Export improperly also lists INSERT, UPDATE, DELETE, and MAKE TABLE queries as possible sources (rather than only tables and SELECT queries) * dbeInt() returns incorrect value for 0 or any negative whole number * dbeSubStr() incorrectly uses 1, rather than the maximum value, for the count parameter if the count is not specified * dbeRunApp() does not correctly handle running of .CMD files * dbeChr() returns incorrect value if called in a macro * ASCII 'ff' (decimal 256) characters in imported data cause random problems during import and when viewing/using resulting table rows * Length attribute of report fields is ignored when displaying data on reports * Vertically scrolled windows in the query designer sometimes cannot be scrolled back into position after closing and reopening the design * Table window positions in the query designer are not always properly restored after closing and reopening the design * Some very long expressions and conditions in the query designer are truncated after closing and reopening the design * Update queries which involve join operations sometimes update the incorrect rows of the underlying tables * Some update queries which involve a join and an update on the "read only side" of a 1-to-N join would appear to execute rather than display the appropriate error message * Attempting to create a new application when OS/2 Warp FixPak 11 is installed sometimes causes and erroneous error and then application can't be created
 www.os2site.com/sw/apps/database/dbup209.zip
Record updated last time on: 11/04/2018 - 16:24

GTranslate

English Dutch French German Korean Russian Swedish

Add new comment