Current JBuilder 4 and AppServer 4.5.x users can now download an updated version of JDataStore from

  http://www.borland.com/jdatastore/
  http://www.borland.com/devsupport/jdatastore/Jds403patch.html

Please notice that if your development does not require fixes and updates provided with this version, we advice you to continue using your current version.

* Note for Windows 2000 Users:

To fix a bug in JDSExplorer where it will fail to be launched in stand-alone mode under Windows 2000 systems, please follow the instructions below:

Open \bin\jdsexplorer.config on a text editor

Add the following line:

  addpath ../lib/beandt.jar

Save the change and close the file

Note of JDBC Explorer changes:

  JDBC Explorer is now called DBPilot.

  To continue sharing connections created with JDBC Explorer
  with JDSExplorer the following changes will be required:

  Launch DBPilot from the Tools menu of JBuilder
  This will create a .dbpilot directory under our profiles
  directory [on Windows systems /WinNT/Profiles/UserName/.dbpilot]

  Copy the contents of .jdbcexplorer/jdbcExplorer.properties to
  dbpilot.properties

What's new in the Early Adopter 4.03 version of JDataStore:

  NOT NULL constraint causes UPDATE to fail when NOT NULL column(s) are not updated.

  The "where" clause of some query statements that are optimized to use
  secondary indexes fail to find rows when the statement is executed more than
  once.

  JDBC connection pool implementation encounters stack overflow under some
  conditions.

  PreparedStatements not closed while saving changes back to a JDBC database
  using a QueryDataSet that joins one or more lookup tables. Causes a "Too many
  cursors open" error when an Oracle database is used in this context.

  JDS Explorer hangs when an attempt is made to import tables from more than one
  external JDBC data source.

  JDataStore Explorer create index case insensitive check box behaves in
  opposite of what it should.

  Daemon JDS thread will hang if the last connection closed has its
  Connection.readOnly() property set to true.

  Sorting DataSet columns using a MemoryStore and a Locale property setting can
  lead to ArrayIndexOutOfBounds exception.

  Carriage returns not allowed inside SQL string literal.

  Query/ProcedureDataSet providers can be slow to release memory.

  SQL Optimizer will sometimes drop selection criteria when there is a choice of
  indexes to use to optimize a query.

  Single quote escapes inside SQL literals had first string segment set to
  zeros.

  Group by not allowed in select used for insert statement.

  Error when accessing two or more ResultSets generated from the same Statement
  instance.

  Quoted range variables forced to upper case if it matches the name of the
  column.