Lisa,

I appreciate the time you took to reply. Your info was useful, but general. Maybe that means I didn't state my goal clearly enough.

I don't know much about HTML and XML, and I don't hope to learn much more about them (for now). My goal is to send report output to Excel, laid out somewhat like the printout, in the simplest, most efficient way.

Copy [reportcursor] to [file] type xl5 is what we're currently doing, but then our users get extra columns which the frx uses for calculations, sorting, group headings, etc. We're working on ways to refine that.

I would be happy to use the HTMLListener instead of the XMLListener, if that's appropriate. In fact I had already noticed that it *might* be, in the little research I've done. I started with the XMLListener because I was told that the Fox team recommended XML for sending to Excel.

You gave good info on some big-picture choices I have. But I hope I can get some more specific answers. What properties or methods should I focus on understanding and adjusting, in either the XMLListener or HTMLListener? Do I need to change the GetDefaultUserXSLTAsString method? That looks pretty intimidating, but I'll give it a shot if that's what's needed. Or should I find (or create) an appropriate object to assign to XSLTProcessorUser?

I'm sorry if I'm misinterpreting the tone of your message, but it sounds like you were partly defending what the class is doing. I didn't mean to attack it; I'm sorry if it sounded like it. I was just whining about how much code there is to get through, to try to learn how to use the class before any documentation exists.

Thanks again for taking time to reply.

Rich Addison