|
|
PlugSys International
LLC
1636 Graff Avenue
San Leandro, CA 94577
(510) 352-2228
Fax: (510) 352-2231
http://www.plugsys.com
|
|
News
Release
|
|
|
|
|
|
|
PlugSys Announces
Open Xbase Connectivity (OXBC)
New
Technology for MaxTM Product Line Delivers
High Performance Access to FoxProTM, dBASETMTables, Index Files
|
SAN LEANDRO, CA-- Since the release of the Max Xbase compiler last year, developers
have made it clear: they want to migrate applications to new operating systems,
the web. But they want to work with existing data stores. To ease migration,
PlugSys International has architected Open Xbase Connectivity (OXBC), a high
performance "straight path" Xbase access technology.
The goal of Open Xbase Connectivity (OXBC) is to deliver optimal access to
other data stores than the native file format included with Max. With the use
of the proper drivers, customers will be able to access SQL database engines
and popular Xbase file formats found in FoxProTM, dBASETM and CA-ClipperTM.
Although some Xbase products provide similar access using the ODBC interface,
OXBC offers a quick and symmetrical path from Xbase command syntax (in applications)
through to the back end database semantics.
"When I started the ANSI Xbase Language Standard Committee (X3J19), I was striving
to perserve the elegant row-by-row navigation that Xbase provides," said Marc
Schnapp, product strategist at PlugSys International. "OXBC realizes this goal
by avoiding an SQL translation layer. This ensures that Xbase developers can
use the language they already know so well, execute Xbase navigation strategies
and enjoy topnotch performance in the process."
As a part of the forthcoming release 2.0 series (Max for Linux, Max DOS32/W
and MaxWeb), PlugSys International will offer customers a driver delivering
on the promise of OXBC. Details will be provided in an upcoming announcement
from PlugSys.
"Developers are telling us they're revising reliable apps and migrating them
from obsolete 16-bit DOS and SCO Unix products onto our 32-bit Linux, win32
and web platforms. Organizations relying on these applications want to continue
using the data file formats they have in place," said Claudio Lavacca, Chief
Software Architect at PlugSys.
PlugSys strived for transparency in the implementation of the access technology.
"Our goal was to avoid adding low level API calls, SQL syntax or translation to SQL set operations when
querying against Xbase data," said Lavacca. "To open a FoxPro table, just employ
the classic USE command.
Max invokes the OXBC driver and you're ready to proceed."
OXBC vs. ODBC
By now, most database developers are
familiar with ODBC, developed by Microsoft as a response to work in the SQL
Access Group. This approach provides a well-regarded virtual access method to
SQL database servers such as OracleTM,
Sybase SQL ServerTM, InformixTM
and Microsoft SQL ServerTM.
- For common Xbase language database transactions, ODBC introduces
performance penalties. The ODBC model is wedded to the set-oriented
nature of SQL. ODBC drivers for Xbase must map record-oriented Xbase operations
into set-oriented SQL semantics.
- To get the most from ODBC, applications should submit SQL queries.
Some Xbase products offer SQL query capabilities
against Xbase tables. In adopting this approach, developers lose the elegant
row-by-row navigation inherent in classic Xbase--and are also likely to sacrifice
performance.
OXBC Is Optimized for Xbase Operations
The common Xbase SKIP command illustrates OXBC's superiority over ODBC (for
Xbase operations against Xbase tables):
|
SQL/ODBC
|
SELECT * FROM customers
WHERE
cust_id = 5505
|
SQL queries return a set of
rows--even when the expected result is a single row.
You need a navigation approach
to reach the "next" record. (This may also entail building a cursor or
view.)
|
|
Xbase/OXBC
|
SKIP
|
Xbase moves as if the data were
in physical space.
|
Migration time and runtime performance
are both optimized when using OXBC. This architecture avoids semantical mapping
by the driver. It eliminates rewriting database navigation code. A SKIP command channeled through an OXBC driver simply moves
a record pointer to the next row in the current Xbase data table image.
ODBC Is Still Significant
ODBC is an appropriate technology for accessing SQL RDBMS engines. PlugSys
International plans to incorporate this interface across the board with an upcoming
release of ODBC connectivity software. With this interface in place, Max developers
will have the ability to invoke the right tool for the job at hand.
Testing OXBC With Max 2.0
Max 2.0 enters beta test shortly along with an Xbase OXBC driver. PlugSys invites
dBASE and FoxPro developers to participate in data access testing by visiting
http://www.plugsys.com/beta.
PlugSys International (www.plugsys.com)
enjoys a decade of development experience based upon a predecessor product line
marketed in Brazil as Joiner. Joiner is still heavily used by DOS and
SCO Unix developers in that market. Max is the 32-bit successor with availability
for Microsoft's 32-bit Windows operating systems and for major Linux distributions.
Max and MaxWeb are trademarks of PlugSys International LLC.
FoxPro is a trademark of Microsoft Corporation, CA-Clipper is a trademark of
Computer Associates International, Inc. dBASE is a trademark of dBASE Inc. Oracle
is a trademark of Oracle Corporation. Sybase SQL Server is a trademark of Sybase
Corporation. Informix is a trademark of Informix Corporation. Microsoft SQL
Server is a trademark of Microsoft Corporation. All other trademarks are recognized
to be held by their respective owners.
