Hello,

I think of using List&Label for all my printing and reporting work. 
This means that a lot of my reports have to be created dynamically as I nor
the user know up front what is going to be printed. That means I need to
use the DOM functionality of List&Label to build the report layouts. 
Before I start building an Xbase++ object model for this, I would like to
know if anybody else has done some work on this and is willing to share it.

Thanks,
Peter

Hello Peter,
please try SBROWSE (download it from http://combifinanz.de/tools), there you 
can see how we managed dynamic reporting with L & L.

> Hello Peter,
> please try SBROWSE (download it from http://combifinanz.de/tools), there you 
> can see how we managed dynamic reporting with L & L.

I did and only this week got a chance to have a good look at it.
As it is, the supplied source does not reveal much about the interface with
L&L.
I noticed that the toolbar has a button to deliver a report. Unfortunately
pressing that button returns an error on my system where L&L15 is
installed.

I don't know for sure, your version is L&L11 and I thought the DOM was
introduced in version 14 or 15.
Looks I'm still on my own writing an Xbase++ interface for it.

Peter

Hello Peter,

We used L&L before, but for our new projects we use FastReport (Frax).

L&L was good but mostly overkill, fastreport delivers everything we need. 

FastReport for Xbase++: http://www.paritetsoft.ru/frax.htm (also a small 
xbase example for download.)


Paritetsoft is also one of alaska's partners like Combit:
http://www.alaska-software.com/tpartners/tp_list.shtm

Kind regards,

Nico Houben
Car-Systems B.V.



Peter Alderliesten <p.alderliesten@solvention.nl> wrote in message 
news:1drpwsbgvy7pw$.1fvfvsp29y9cf$.dlg@40tude.net...
>Hello,
>
>I think of using List&Label for all my printing and reporting work. 
>This means that a lot of my reports have to be created dynamically as I nor
>the user know up front what is going to be printed. That means I need to
>use the DOM functionality of List&Label to build the report layouts. 
>Before I start building an Xbase++ object model for this, I would like to
>know if anybody else has done some work on this and is willing to share it.
>
>Thanks,
>Peter

Nico,

> We used L&L before, but for our new projects we use FastReport (Frax).
> 
> L&L was good but mostly overkill, fastreport delivers everything we need. 
> 
> FastReport for Xbase++: http://www.paritetsoft.ru/frax.htm (also a small 
> xbase example for download.)

I have bought Frax as well. I found the documentation very poor (to say
nothing more).
What stopped me implementing Frax is that I could not keep the results of
one report open and run another report.

The implementation of L&L is far better documented and consistent. I only
think they don't have many users using the DOM functionality.

Peter

hi,

> I think of using List&Label for all my printing and reporting work.

im not shure who did use L&L activeX, but on Devcon 2007-Berlin Tom Liehr
gave me his DLL Version from his Session.

greetings by OHR
Jimmy

We have completely converted our project from using the DLL version to the
ActiveX version. Is this different from DOM?

Sorry just not familiar with DOM.

Mark Sergent
InnSource Solutions Inc.
mark@innsourcesolutions.com

Mark,

> We have completely converted our project from using the DLL version to the
> ActiveX version. Is this different from DOM?
> 
> Sorry just not familiar with DOM.

I have made a lot of progress (almost finished) writing an object oriented
wrapper around the DLL-functions, so I don't need to bother about
registering an OCX on all kinds of user machines.

Yes, apparently with version 15 (I don't have an earlier version) a
Document Object Model was introduced in List&Label. It opens the
posssibility at runtime to analyse, create and/or modify a project file.
For me it means that I can now offer a user a screen where he can pick any
number of columns to print and I just modify the project file on the fly,
to take care of these columns.

The only thing is that combit just made a start with it. I have a feeling
that they just opened up what was already there. They should add some
functionality for more flexibility. But I am sure that will come when the
DOM get used. I don't think it has many users currently.

Peter