Re: C-ISAM - SE Composite index Problems

In article <46m280$177@cssun.mathcs.emory.edu> johnl@informix.com (Jonathan Leffler) writes: >Hi, > >You need to analyse the '.idx' files of an SE-built C-ISAM file because >they are not the same as you would normally build with C-ISAM. I attach >(old) C-ISAM code which analyses the indexes -- no guarantees that it works >8 or so years after it was written. Anyway, index 0 is different in SE >from that you'd expect if using pure C-ISAM. > >The best way to handle interworking C-ISAM and SE is to have SE create the >C-ISAM files and to have the C-ISAM application access exactly the files >provided by SE. It is the '.idx' files which differ; the '.dat' contents >are the same. > I am also trying to use C-Isam files and I can't really understand about the index difference. I defined my db tables to mirror the C-Idsam file descriptions and then copied the C-Isam files on top of the db tables (both .dat and idx). I can access the data in these tables, as long as queries are simple. But as soon as I have a complex query the whole thing gives up and I get a "network receive failed" message. What I did to overcome this was 1: tried experimenting with the column definitions for numerics... trying small integers, integers and messing around a fair bit, as I believed the problem was one of incorrect data typing. But this didn't work so I ended up using 2: unloading from the db I'd copied the C-Isam files into, to a "clean" db, defined identially as the one i had originally set up. This works of course but it's slow. It takes me two hours to do this copy, unload, load operation. I'd like to hear from any one else who has had to use C-Isam files in an SE db. But surely if the index files are different my method of copying would not work???? --Kate >