Main   Products   Offshore Outsourcing   Customers   Partners   ContactUs  
JDBC Databases
  HXTT Access v5.2
  HXTT Cobol v2.1
  HXTT DBF v5.2
  Buy Now
  HXTT Excel v4.2
  HXTT Paradox v5.2
  HXTT Text(CSV) v5.2
  HXTT XML v1.2
Offshore Outsourcing
Oracle Data Import/Export
DB2 Data Import/Export
Sybase Data Import/Export
Free Resources
  Firewall Tunneling
  Search Indexing Robot
  Conditional Compilation
  Password Recovery for MS Access
  Password Recovery for Corel Paradox
  Checksum Tool for MD5
  Character Set Converter
  Pyramid - Poker of ZYH
Heng Xin Tian Tai Ltd. of Beijing City (abbr, HXTT)

Oscar San Martin
2010-08-01 15:49:11.0
Hello, sometimes, we need to re-index all my fox tables ( with fox sentence ) in order to generate a particular report.....sometimes this is not necessary.....because sometimes my report is empty.....but after re-index, all data are shown in the report....

why can this happen?....our mainframe is sco unix 5.0 with foxplus tables... we have all cgp files configured correctly


HXTT Support
2010-08-01 17:11:03.0
>we have all cgp files configured correctly
CGP file be mainly used for Clipper's NTX index files. If you're using only one structure CDX file for Foxpro table, you needn't it. If you have more than one CDX files for Foxpro tables, you need CGP file to help you.

>sometimes, we need to re-index all my fox tables ( with fox sentence )
When you meet issue, you can try "REINDEX all on oneTable;" through HXTT DBF to make sure that HXTT DBF can do it too.

>why can this happen?....our mainframe is sco unix 5.0 with foxplus tables...
According to Released Version Log
v3.1.012 provides FOXPRO4UNIX lock type for Foxpro2.6 on SCO Unix.
v3.1.035 uses lazy load for CDX format index on Xbase compatible mode.
v4.0.049 distinguishes empty value from null value for CDX index format.
v4.2.013 fixed a bug on CDX compound format index file, which will sometimes set wrong index node information for specific complicated string index expression on insert operation.
v4.2.039 solved a CDX multiuser compatibility issue with VFP, which VFP will produce specific duplicated index information sometimes on mulituser mode.
v4.2.155 provides lockType=Alaska connection property to detect Alaska Software's CDX incompatible format.
Maybe your driver is too older, and meet one of those issues?
Oscar San Martin
2010-08-02 06:40:26.0
We're using DBF_JDBC30.jar.....our index files are "IDX"...


HXTT Support
2010-08-02 06:46:40.0
>our index files are "IDX"...
IDX format can be uncompressed index (another format) and compressed index (similar to CDX format).
Oscar San Martin
2010-08-02 06:52:38.0
I'm going to try a new version 4.0....

Search Key   Search by Last 50 Questions


Copyright © 1999-2017 Heng Xin Tian Tai Ltd. of Beijing City. | All Rights Reserved. | Privacy | Legal | Sitemap