FPD26(.CDX)<>100%FPW25B(.CDX)

[Andy888]

Hi!

When I create a compound index or reindexed(.CDX) a big database file by using Foxpro for DOS 2.6. Foxpro for Windows 2.5B counld not open it with a correct index and show an error message(some small CDX work fine). It's cause my problem. Now, I know that Foxpro for Windows 2.5B's CDX file is not 100% compatible with Foxpro for DOS 2.6.

I have Foxpro for DOS 2.6 and Foxpro for window 2.5B,
So far, I need a version Foxpro for Window 2.6 same as DOS 2.6 version. Due to I need to use Foxpro for Window to open databases through a Win2K terminal server for remoted clients. Local users still use DOS version Foxpro on a novell server. Because Foxpro for Windows 2.5B could not be upgraded to 2.6. Have someone can just send me a copy of FOXPROW.EXE version 2.6 file to solve my problem? I will be appreciated.

Andy

 

[rgbean]

Andy,
I never found any incompatibilities between 2.5 and 2.6 index files (the official MS documentation shows the structures are the same!). What exactly are you using for index expressions? Are you using any system functions or UDF()'s?

FPW 2.6 is still a copyrighted program (even though it is no longer supported), and sending you a copy would violate MS licensing.

Rick

 

[Andy888]

Rick,

Thanks for your reply. I used FPD2.6's "COPY INDEXES ALL" command to create a compound index from original numbers of single index files which belong to a master data base. After this CDX file be created. I tried to use FPW2.5B to open it. It showed an error message. Only way I can solution this problem is I need use FPW2.5b to rebuild this CDX file (REINDEX) again. Then let this CDX file can be used for FPD2.6. I had created five CDX files for five different DBF files. I had three CDX files had an error message. I compared both these CDX files's size which created by FPD2.6(use COPY INDEXES ALL command created) and FPW2.5(use REINDEX command to reindex CDX file which just creaded by FPD2.6 COPY INDEXES ALL command). There has different file size. I can make sure FPD2.6 and FPW2.5b's CDX file is not comptible.

By far, I believe MS will not sell this product even I want to spend money to buy it. If I can prove this is a bug. I don't know MS can treat this case is a special case or not?

 

[rgbean]

OK Andy, I just tried to duplicate what I think you did, and I'm getting no errors.

In FPD 2.6a:
1) Created a table with 6 fields (TEST_DX.DBF)
2) Created an index (.IDX file) on each of the first 5 fields
3) Loaded 20,000 records with semi-random data in the 6 fields
4) COPY INDEXES ALL TO TEST_DX.CDX
5) Closed the 5 .IDX files, and I could successfully SEEK() on records in any of the tags in the .CDX file.

Close FPD 2.6a (and obviously the table)

In FPW 2.5b (patched for a "Fast CPU&quot:
1) USE TEST_DX.DBF
All the indexes were in place, and I could successfully SEEK() on records in any of the tags in the .CDX file. If I set the ORDER TO 0, I could also Browse the table in "natural" order.

Perhaps if you could explain how what you did was different, or what the index tag expressions are (mine were simple single character fields).

Rick

 

[Andy888]

Rich,

Thank you to took time to do a test on my case. First of all, I use FPD 2.6(not 2.6a). Second, the database record over 220,000 records. Third, Index file I created since 16 years ago by useing DBASEIII. But, I had modified database structure many times through Foxbase and Foxpro 2.0, Foxpro25b and Foxpro26.

I found out the backup file which has a problem to open the CDX file and redo a test. The error message show "INDEX DOES NOT MATCH TABLE, RECREATE INDEX." Then, I need use FPW2.5b to reindex again.

I will do some tests to find out what condition FPD2.6's CDX file is not 100% compatible with FPW2.5b. If I have a result, I will let you know. Thanks again.

Andy