Answers in this category:
Early Adopter JDataStore 4.03 Available for Download
Where is Borland's JDatastore FAQ?
After installing JBuilder 5 and installing the license for JDataStore I have the following problem. If I start the JDataStore the within JBuilder 5 it starts perfectly for the Tools|JDataStore Server. However if I try and run it from Windows directly: Start|Programs|JBuilder 5|JDataStore Server it doesn't start.
I used the JB5 Archive Wizard to create a jar, selecting "Include Everything" for the JDatastore library. I can run the application with "java -jar dbTest.jar" just fine. However, I want to exclude the JDatastore classes and package those jars separately. I can't get the application to work!
I want to deploy JDatastore on a server. What are my licensing options?
I bought a book entitled "RAD Development with JBuilder 4/5/6" which includes a cdrom with an Enteprise Eval and JDatastore. It is asking me for a JDatastore registration key and I can't find one anywhere.
Is it possible to run JDataStore apps on the Palm OS?
JDataStore 5.01 Trial available for download
Where/how can I purchase deployment licenses for JDatastore?

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.

  http://community.borland.com/article/0,1410,19685,00.html

Both JDSServer and JDataStore Explorer are launched with an option that points to its documentation. It used to be -h now it is -doc.

So, in order to fix this bug you need to change the invocation of both tools from:

  JdsServer -h=..\doc

  JdsServer -doc=..\doc

Here are the steps for Windows 2000:

  1. Start | Settings | Taskbar & Start Menu
  2. Select the Advanced tab
  3. Hit the Advanced button (see how advanced you are! :)
  4. Select Startup | Programs | JBuilder
  5. In the Content pane right click on top of the JdsServer entry and select Properties.
  6. Modify the command-line as indicated above.

Repeat the 5 and 6 for JDSExplorer using:

  JDSExplorer -doc=..\doc

to replace the original line.

For NT 4 Users:

  1. Start | Settings | TaskBar
  2. Select Start Menu Program tab
  3. Hit Advanced button (not so advanced...)
  4. Look for Start Menu | Programs | JBuilder 5

  

  Exception occurred during event dispatching:
    java.lang.NoSuchFieldError: qb
    at com.borland.datastore.DesignerHelp.setCommitOnDemand(Unknown Source)
    at com.borland.dbtools.dsx.DataStoreExplorerController.b(Unknown Source)
    at com.borland.dbtools.dsx.DataStoreExplorerController.a(Unknown Source)
    at com.borland.dbtools.dsx.DataStoreExplorerController.kb(Unknown Source)

  Add the following line to the JDSExplorer.config (and JDSServer.config) file:

    addpath ..\lib\beandt.jar

This will fix the second problem.
2001-Jul-02 3:11pm gyles19@visi.com

I've tried setting the Classpath with

  $ java -classpath /x/x/jds.jar ... -jar dbTest.jar

I've tried adding the JDatastore jars to my CLASSPATH environment variable... Nothing seems to work!

Answer:

Java's -jar parameter overrides the -classpath parameter: you can't use both parameters at the same time. You must adjust the jar's manifest to include the necessary classpath so that the -jar parameter finds it properly.

  Manifest-Version: 1.0
  Main-Class: package.MainClass
  Class-Path: dx.jar jds.jar jdatastore.license

Another way to launch the application is to not use the -jar parameter at all.

  java \
    -classpath dbTest.jar;\
              /jbuilder5/lib/jdatastore.license;\
              /jbuilder5/lib/dx.jar;\
              /jbuilder5/lib/jds.jar\  
    package.MainClass

Replace "package.MainClass" with the package.class taken from your Manifest.

(I've broken the command up into pieces using unix shell syntax for readability. This would normally all be on one line.)

2001-Aug-02 8:44am gyles19@visi.com

However, Jose Elias wrote this response:
First of all, the only way to get JDataStore is by getting it with JBuilder Professional or Enterprise, it is not sold stand-alone as far as I know (which is REALLY bad from Borland's part, since I think JDataStore is an amazing product in its own right). When you get it you also get a free 1-developer unlimited-use license. This is NOT a deployment license (i.e.: you can use it for testing your applications, but if you start using it for real you have to pay).
Second, If more than one developer wants to develop with you, you have to buy another license for 100 dollars. Each additional developer is US$100.
Third, when is time to DEPLOY the application, you have two choices depending on your application architecture: You can buy a license for EACH user of JDataStore for US$100 per user, OR you can buy a server license for US$2500 which you can use to connect as many users as your application allows. This means that if you have 250 or more users, you should buy the server license, not just because it saves you money, but because it is much more convenient to manage.
2001-Dec-30 10:46am gyles19@visi.com

The publisher failed to provide registration keys for the cdrom they bundled and Borland doesn't make JDatastore development reg keys available any other way. The cdrom in the book is customized by the publisher, it isn't Borland's original. The setup_*html files on the cdrom I saw were half-Personal and half-Enterprise-eval.

Contact the publisher of that book directly. They need to publish an errata to the book's cdrom that will provide the JDatastore developer registration keys needed.
2002-Apr-08 9:06am gyles19@visi.com

Currently, JDataStore runs on the iPaq and other devices with similar memory availability (16 MBytes of RAM or larger).

The iPaq 3800 series includes a JVM.
2002-Apr-11 8:19am gyles19@visi.com

http://www.borland.com/jdatastore

Hit the yellow "Try it Now" button on the left.

------------------------------------------------------------------
Important:
------------------------------------------------------------------

This is a standalone version of JDataStore designed to be installed in its own folder.

Borland Enterprise Server 5.01 users already have this version of JDataStore included with their respective products.

------------------------------------------------------------------
To upgrade from a prior version follow the steps below
------------------------------------------------------------------

 install this version of JDataStore on its own directory;

 make a backup copy of the following jar's from either your \JBuilder\lib, or   
 \BorlandEnterpriseServer\lib subdirectory

 beandt.jar
 dbtools.jar
 jdsserver.jar
 jds.jar
 dx.jar
 jdsremote.jar

 replace with the ones from \JDataStore5\lib subdirectory

To verify which version of JDataStore you have, launch JDataStore Explorer or JDataStore Server and open the Help | About menu option.

For more information, check the release_notes.html file at the install directory.

------------------------------------------------------------------
Bug Fixes and Improvements
------------------------------------------------------------------

1) Incorrect values in result set of| select query with an order by clause from a table with an autoincrement column.

JDataStore crash recovery can corrupt database when system crashes while freeing up deleted files/tables or when deleting large blobs.

This defect has been fixed for 5.02.| Although most applications do not encounter this defect, the database can be corrupted when an application does encounter this defect.|

Here are the circumstances in which this defect can be encountered.| Note that all 3 conditions must be met for the defect to occur.

a) Your database has dropped tables with space that has not been released. When a JDataStore table is dropped, the space allocated to it is not immediately released.| The table is marked as deleted and JDataStore will release the space as new allocations are requested using a background FreeStreams thread.

b) The FreeStreams thread used to free up space allocated| to dropped tables is in the process of releasing blocks allocated to dropped tables

c) The JDataStore FreeStreams thread is not able to commit its transaction due to an application being stopped in the debugger, operating system crash or some other failure that does not allow the FreeStreams transaction to commit.| In this case the JDataStore crash recovery process can corrupt your database due to the fact that the FreeStreams transaction has logged an incorrect undo record.

It is recommended that JDataStore applications upgrade to 5.01 if possible to avoid this defect. For older installations of JDS, you can prevent the likelihood of encountering this defect by packing the JDataStore database after a table is dropped so that the FreeStreams thread will never need to be activated.

The JDataStore database verify can detect database corruption.| Verify can be activated through JdsExplorer or programmatically via com.borland.datastore.StreamVerifier.verify() method. Corrupted databases can be salvaged by using the JDataStoreExplorer Tools|Pack menu option or by using the com.borland.datastore.DataStoreConnection.copyStreams() method to copy the contents of the database into a new database.

By default, JDataStore 5.01 will create new databases with a new file format version of 9.| This keeps older versions of JDataStore classes from accessing newer JDataStore databases since the old versions of JDataStore classes have this defect.| Applications upgrade databases to file format version 9 by using the JDataStoreExplorer Tools|Pack menu option. Note that the JdsExplorer info tab displays the file format version next to the "Version:" label.

2) New JDataStore transaction log files cannot always be created under Win98.
When this occurs, applications typically encounter the following TxException error message: "com.borland.datastore.TxException: Cannot create new log files for JDataStore because a file with the name of C:\tmp\TestDebitCredit_LOGA_0000000000 already exists."

3) java.sql.DatabaseMetadata falsely returns an empty resultset when a table is created with the same column being the primary key and an autoincrement field.

Fixed.

4) Autoincrement value skips next value when database is shutdown and then restarted.

If values 0, 1, 2 where used for the autoincrement field for the first three rows added to a table, then when the database is shutdown and restarted, the next row added will now receive a value of 3 for its autoincrement field instead of 4.

5) The in-process local JDBC driver now restricts the number of open ResultSets per Statement to one.

This is behavior specified by the JDBC standard.| The TCP/IP based remote driver was already enforcing this behavior.

6) No pre allocation of blocks leading to a smaller size for .jds files

------------------------------------------------------------------

2002-Apr-19 6:58am gyles19@visi.com

Regarding JDataStore licenses, currently Deployment licenses of JDataStore 4 and 5 can be purchased at:

  http://www.borland.com/shop/index.html?catid=3468&groupid=1668

Development licenses will soon be available at this same page.
2002-Apr-23 8:36am gyles19@visi.com