>If you are that keen to see it work that way ...

I'm EXPECTING to see it work that way, and so should all of us! After all, GenrepoX promises to enhance the VFP report writer, not to make it worce!

>why dont you jump in and do the coding ...

I think the developer should do the code fixes as that's part of the obligation when publishing software. The users (we) should do the testing and bug reporting!

>Its more about time management me thinks ... maybe Markus doesnt have the
>time right now ...

I think it's more about lack of commitment to enhancing the product.

>Using the driver model you should be able to build a
>driver that does exactly what you want...

I still think the fix to this particular problem belongs in the core product, not in a driver extention! After all, this problem is about GenRepoX not respecting the FRX width setting for extended detail lines.

Look, I don't want to be a pain in the ass to anybody. I just want to be taken seriously when reporting a problem with an otherwise exellent product. To make it work better for all of us.

Kind regards,
Vidar