Recent changes to feature-requests

Publish ECCN for xBaseJ

Chris Lott — Fri, 04 Mar 2016 13:42:11 -0000

Please consider publishing an Export Control Classification Number (ECCN) for xBaseJ. To figure out the right ECCN for software, you read the Commerce Control List (CCL) (Supplement No. 1 to Part 774 of the EAR) and try to figure out where the software best fits. In the happiest possible outcome, you will find an exemption (this is better than an exception) that applies to your situation, so that piece of software is not subject to export control, and therefore it has an ECCN of "EAR-99".

You may wind up writing a statement something like this:

The [XYX Software] primary functions do not include information security; sending, receiving or storing information; or networking; and it is not a computer, operating system, or parts or components therefor. Hence, [XYZ Software], excluding 3rd party software, is not controlled for export per Note 4 to Category 5, Part 2 (Supplement No 1 to Part 774)

This may help:

https://www.bis.doc.gov/index.php/licensing/commerce-control-list-classification/export-control-classification-number-eccn

Thanks for considering it.

#2 Merge my xBaseJ improvements into your code

Joe McVerry — Mon, 08 Sep 2014 12:05:51 -0000

Feel free to post the changes in an attachment. For my convenience use Eclipse patch files.

Merge my xBaseJ improvements into your code

R. v. d. Borne @ CGM — Tue, 26 Aug 2014 16:04:19 -0000

I'm a software programmer of compugroup medical company in Germany.
We're just writing a migration software to migrate an old dbase version of our software to the next generation. The old software is based on sequiter codebase (dBase IV).

As I had problems to import some of our tables, I did some improvement/enhancement work for xBaseJ.
I would appreciate if you could merge this into your code to avoid code branching and merge conflicts in the future.
Please contact me: rbn@compugroup.com or via ticket system.

What I did is dBase indexing improvements:

It is possible to have index files in another directory than the dbf file.
This is helpful if you need to generate a temporary index without changing the index
in the original directory. This is useful if you can't use the original index
due to missing special dbase features in xbaseJ.
Hint: This only will work, if you use the dbf table in read only mode.
The dbf file is read only, but the index can be created in the different directory
Skip incomplete / faulty index (tag) expressions of an MDX file, but use tags that do
not make problems (available in read only mode)
Support index '+' and '-' concatenation of columns in index expressions
Support ascending and descending order in an index expression
Implemented a progress view for performing the first step of the reIndex method
Support of function calls embedded in index expressions
Currently the following functions are being supported:
DTOS, // convert date to string YYYYMMDD
STR, // convert number or double value to string
UPPER, // should be clear
SUBSTR, // extract a substring out of a column
RECNO, // return the current record number
Other methods easily can be added if they are needed, see:
http://www.data-tech.com/help/faxsdk3/dBASE_Expression_Functions.html
```
Example for index expressions containing dbase functions:
"STR(PatientNo,15,0)-STR(Quarter,5,0)-STR(SerialNo,15,0)-DTOS(Date)-STR(SPos,5,0)-STR(RECNO(),12,0)"
```
Handling of int-to-short casting problems (max value of type short exceeded)
Removed System.gc() call as this slows down the reindexing process.
Simplified handling of boxed types

Support For Compact indices (.CDX)

Anonymous — Fri, 13 Jul 2012 17:39:06 -0000

adding support for the compact index (.cdx) file for visual fox pro based applications.

Here is the file structure for a cdx: http://msdn.microsoft.com/en-us/library/s8tb8f47\(v=vs.71).aspx