This is not a new subject, but yet another bug in this crappy tool called Document Composer. I've got 3 tables: station, location and site and I'm chaining from station_code in station to station_code in location. From there I' sending the display value to pick up all sites belonging to that location. Just adding to the frustration, in the composer all rows in the last box appear, making you happy and think you finally got it work. In runtime however, only the first one shows.

The population of the boxer is made in external procedures, since I've had a few issues using Master files with Chrome and FF.

Anyone has a good idea what's going on?

Tia
Håkan

Håkan,

I have some chained controls that seem to work, though I haven't tried three chained controls yet.

So, you have Station, Location and Site controls that are chained. Then you have one external fex that retrieves all the columns and rows. This should look something like this:

JOIN station_code  IN station TO station_code  IN location AS J1
JOIN location_code IN station TO location_code IN site     AS J2 

TABLE FILE station
SUM
MAX.station_name
MAX.location_name
MAX.site_name

BY station_code
BY location_code
BY site_code

ON TABLE PCHOLD FORMAT XML
END

Then you would assign this Dynamic External Procedure to each of the three controls, picking the appropriate columns for the Value field and the Display field. Check the "Check for duplicate values" checkbox.

If you've done all this then I'm not sure what's going wrong. If I haven't described your situation properly, please correct me.

Thanks,

Embedded procedures work fine with FF and Chrome for us. Is that what you're talking about when you say "using master files"?

Perhaps you're only seeing the problems with the older WF 7.6.10?

Or perhaps you're attempting to enforce a different sort order to how the TABLE FILE block gets generated in the embedded procedure's body? That will break chaining, yes. Don't touch the generated code if you're chaining! Even adding an extra WHERE-clause can cause problems.

If you want a different sort order than the one that the generated TABLE FILE uses, you are supposed to select the sort order using the check-boxes in the embedded procedure properties (which moves the burden of sorting the list-boxes to Javascript).

The alternative is indeed to use external procedures, but those have their share of problems as well as you found out.

Thanks guys, I have'nt had time to deal with this for a couple of days. Francis, the JOIN solutio worked fine. Wep, I used an external proc, mainly because I prefer not to enter the Composter to often. Once you've got it working, you better not touch it....
Anyway, I've got another problem, which is "only" a performance problem. We've got about 25K sites and IE got problems retrieving that number of rows without displaying that question if you wan't to kill the script. Chrome does'nt have that problem (surprise?). Any good ideas?

Håkan