Notes pertaining to the maintenance and publication of this JRAGAN.com web site.

This is a legally copyrighted work,
so none of it can,
legally or honorably,
be copied, used, or claimed by anyone other than the owner.


An Executive Brief Covering CoreReader
An Example Of My Work

CoreReader Technology
Copyright 2001 - 2019 John E. Ragan.

__________________________________________________
__________________________________________________

CoreReader
Brief

CoreReader allows access to data regardless of where or how it is stored.

_____________________

* Objective *

1. Universal data access without regard to name brands, type of software, or type of hardware.

2. Done through a graphic display for ease of use.

_____________________

* Point And Click Data Access *

Connecting to a data source prompts CoreReader to load all of the source's data objects. He displays them in scrolling windows.

Using the mouse, the user :
      Selects one or more tables.
      Selects columns from the tables.
      Selects SQL operations for the query.
      Presses the do-it button.

_____________________

* Output *

Data is delivered when the do-it button is pressed.

Output defaults to an on-screen scrollable data grid that can sort, find, etc.

Output can be directed to text, html, xml, etc. in an on-screen editor or into a file.

_____________________

* SQL Tutor *

CoreReader uses the point-and-click selections to build a SQL statement internally.

Those wanting to learn SQL can display each SQL statement that they create by pointing and clicking.

That display is interactive, so advanced users can use it to enhance the SQL before running it.

_____________________

* Universal Sources *

Database managers, spread sheets, mainframes, desktop PC's...

Any data source that has the industry-standard ODBC interface.

_____________________

* Connecting To Sources *

Data source connection is sometimes complex, so a GUI form walks the user through the process.

On-line examples show how to connect to source types, brand names, and connection types. Examples can be edited for new connections.

In multi-user installations, the administrator can create connections and share them with users. (Controlled by the security.)

_____________________

* Working Libraries *

When a connection is made, it is always automatically stored. It can later be selected from a list by a point-and-click that makes the connection.

A query can be saved by the user. ( Creating a complex SQL query can take days, and sometimes even weeks, to build and debug.) It can later be selected from a list by a point-and-click.

_____________________

* Job Server *

The internal job server runs unattended jobs such as backup, file movement, database extraction and insertion, external programs, etc. It has its own scheduler.

A GUI assists with job creation and allows visual monitoring.

_____________________

* Data Gateway *

It has an unattended data gateway to serve specified connections to other systems.

_____________________

* Administration *

An administration module configures the system, controls security for multiple users, controls data gateway security, and controls job server access. ( CoreReader blocks all data source updates.)

_____________________

* Documentation *

Yes. In web pages and an internal pop-up viewer.

The documentation is in three volumes :
      Basic user operation.
      Advanced administrator guide.
      Server administration.

_____________________

* Testing *

Thousands were downloaded to every continent on the globe.

It was tested against every database manager, type of computer, spread sheet, brand name, etc. until attention shifted to the AxleBase project. The most interesting feedback came from mainframe users.

Its job server runs 24-7 in production support in the AxleBase lab.

_____________________

* Internal Database *

AxleBase.

CoreReader was run with Paradox, Oracle, MS Access, MsSQL, and MySQL until AxleBase was finally available. ( Since work on it was stopped, AxleBase is not thoroughly integrated. )

_____________________

* Error Handling *

This system was built prior to the development of the AxleBase error handling technology. A retrofit was attempted with limited success.

__________________________________________________
__________________________________________________

CoreReader
Administrative Section

* Known Installations *

CoreReader was originally offered as a free download on its web site. There were thousands of downloads into at least 59 countries.

Click   HERE   for a list of known country homes.

* Licensing *

Not for sale or license. It is not commercially viable.

* Project Purpose *

To test the concept of universal data access and ease-of-use.

* Personal Notes *

Concept development, design, and coding are entirely mine. The commercial systems on the market and the open-source hordes that give free software to big business came later.

* Project Status *

Project is complete.
      But it has not been updated for chqanges required in ODBC, OLEDB, and other protocols.

History :
      Began in 2001.
      Last update was in June 2007.
      Stopped at the AxleBase conception.
      The internal database manager gets upgrades.
      CoreReader.com web site was taken down in July of 2012.

Project statistics :

23,952	lines of code.
894,655	bytes in code.
7,026	comment lines.
16	classes.
989	functions.
15	user GUI forms.

( Reported by Seepper. )

__________________________________________________

Technology and web site
Copyright 1999 - 2022 John Ragan

Web site is maintained with Notepad.
By intent, so don't bother me about it.