I have been working on a problem involving R&R report writer.  I have dbf's 
and cdx's created with the FOXCDX database engine that is the default engine 
in WAA.  The indexes work properly for dbseek(), etc. However, R&R is unable 
to use the tags in these files to connect two dbf's in a parent:child 
relationship.



Bruce Carroll is using R&R successfully with XBase++ created CDX's.  He 
generously sent me some test files and the script to build a simple report. 
This works perfectly, but when I build the same indexes within WAA it 
breaks. I have looked at the two CDX files in a hex editor and they are very 
different. One tag uses only text, i.e., the person's name.  The data in the 
good cdx is readable text.  The data in the bad cdx is unreadable.  My one 
guess is that somehow SET CHARSET is involved in my problem, but I don't 
have the slightest clue about where to go after that.  Any suggestions 
appreciated.  Any explanation of what CHARSET is operating with the default 
FOXCDX in WAA is also solicited.  Thank you.

Hi Bruce,
What way are you using R&R, are you using their asp code or RunShell() R&R?
If you are using asp, it will not work.
Regards,
Vladimir

"Bruce Anderson" <banderson@graphical-db.com> wrote in message 
news:Nm$iA%23g7FHA.6152@S15147418...
>I have been working on a problem involving R&R report writer.  I have dbf's 
>and cdx's created with the FOXCDX database engine that is the default 
>engine in WAA.  The indexes work properly for dbseek(), etc. However, R&R 
>is unable to use the tags in these files to connect two dbf's in a 
>parent:child relationship.
>
>
>
> Bruce Carroll is using R&R successfully with XBase++ created CDX's.  He 
> generously sent me some test files and the script to build a simple 
> report. This works perfectly, but when I build the same indexes within WAA 
> it breaks. I have looked at the two CDX files in a hex editor and they are 
> very different. One tag uses only text, i.e., the person's name.  The data 
> in the good cdx is readable text.  The data in the bad cdx is unreadable. 
> My one guess is that somehow SET CHARSET is involved in my problem, but I 
> don't have the slightest clue about where to go after that.  Any 
> suggestions appreciated.  Any explanation of what CHARSET is operating 
> with the default FOXCDX in WAA is also solicited.  Thank you.
>
>
>
>

Using runshell() and it is "working".
At present, I have R&R building its own indexes everytime it runs a report. 
Very wasteful, very time consuming.  This problem's solution is in exactly 
how WAA makes CDX files.  I just don't know where to take it after 
discovering that the WAA cdx contents are completely different from what I 
would expect.

I've had problems running R&R reports and indexes created with Xbase++ and 
it's usually down to the fact that the collation table is stored in the 
index file which R&R doesn't like.

It sounds lilke the indexes you are creating with WAA are including these 
and hence your reports don't work.

Not sure how you can tell WAA not too include the collation table to test if 
that is the problem.

Jeremy


"Bruce Anderson" <banderson@graphical-db.com> wrote in message 
news:YhLvz607FHA.7860@S15147418...
> Using runshell() and it is "working".
> At present, I have R&R building its own indexes everytime it runs a 
> report. Very wasteful, very time consuming.  This problem's solution is in 
> exactly how WAA makes CDX files.  I just don't know where to take it after 
> discovering that the WAA cdx contents are completely different from what I 
> would expect.
>

Jeremy,

> I've had problems running R&R reports and indexes created with Xbase++ and 
> it's usually down to the fact that the collation table is stored in the 
> index file which R&R doesn't like.
> 
> It sounds lilke the indexes you are creating with WAA are including these 
> and hence your reports don't work.
> 
> Not sure how you can tell WAA not too include the collation table to test if 
> that is the problem.

You can use the dbeInfo() functio to configure WAA and FOXCDX.  The best
place to do this is either in an INIT procedure or the _register()
function.  At the time your package DLL is loaded, WAA has already opened
it's own tables, so they will be using the configuration that WAA requires.

Regards,

Phil Ide

*******************************************
*   Xbase++ FAQ, Libraries and Sources:   *
*   goto: http://www.idep.org.uk/xbase    *
* --------------------------------------- *
* www.xodc.org.uk - openSource Dev-Center *
*******************************************

I'm not round. I'm an oblate spheroid.