Hello,

In designmode, a user can save the report under a new name using "Save as" 
in L&L.
I envoke the designer as follows:

LlDefineLayout(::hJob, SetAppWindow():GetHWND(),"Design " + ::name, ::type, 
::Path + ::filename)

After terminating the designer, how can i get the latest saved report?
I tryed: LlDesignerGetOptionString(), but the docs say it only works wen in 
designer mode.

Regards,
Jack Duijf

Maybee save date and time when invoking designer and when back from designer 
check all files in directory for filedate and filetime inbetween.

Because of this I disabled the possibility to "save as" in L&L. My programs 
have a DBF that stores filename, folder, type (list, card, label) and some 
other informations inside and if a user wants to change filename of a report 
he has to do it here. So I allways have control over the report names and 
other L&L forms.

Klemens

<Jack Duijf> schrieb im Newsbeitrag 
news:c81ff1$57a3a659$3a772@news.alaska-software.com...
> Hello,
>
> In designmode, a user can save the report under a new name using "Save as" 
> in L&L.
> I envoke the designer as follows:
>
> LlDefineLayout(::hJob, SetAppWindow():GetHWND(),"Design " + ::name, 
> ::type, ::Path + ::filename)
>
> After terminating the designer, how can i get the latest saved report?
> I tryed: LlDesignerGetOptionString(), but the docs say it only works wen 
> in designer mode.
>
> Regards,
> Jack Duijf
>
>
>

Klemens,

> Maybee save date and time when invoking designer and when back from designer 
> check all files in directory for filedate and filetime inbetween.
> 
> Because of this I disabled the possibility to "save as" in L&L. My programs 
> have a DBF that stores filename, folder, type (list, card, label) and some 
> other informations inside and if a user wants to change filename of a report 
> he has to do it here. So I allways have control over the report names and 
> other L&L forms.

Did you think of saving the actual L&L files in a dbf as well, because
that's what I'm thinking of doing. No random files, nobody accidentally
deleting or overwriting them...

Peter

Am 03.02.2011 10:47, schrieb Peter Alderliesten:
> Klemens,
>
>> Maybee save date and time when invoking designer and when back from designer
>> check all files in directory for filedate and filetime inbetween.
>>
>> Because of this I disabled the possibility to "save as" in L&L. My programs
>> have a DBF that stores filename, folder, type (list, card, label) and some
>> other informations inside and if a user wants to change filename of a report
>> he has to do it here. So I allways have control over the report names and
>> other L&L forms.
>
> Did you think of saving the actual L&L files in a dbf as well, because
> that's what I'm thinking of doing. No random files, nobody accidentally
> deleting or overwriting them...
>
> Peter

Peter,

I store the project files as they are, my programs use an special 
subfolder to store those files inside. I have a DBF that stores the 
filenames of the L&L-files ond some other informations about the 
projects inside. To choose a file the user just has to browse this DBF 
and choose the L&L-file he wants to merge with his data and print.

But because many of the printjobs that will be done with these 
L&L-projects have hundreds and somtimes thousands of pages I store 
before printing all data that has to be printed into another dbf as a 
printjob. Every printjob has such a DBF with one record for every page 
or dataset that has to be sent to L&L. Depending on the data those print 
jobs can than be sorted (indexed) by name or zip-code or invoice-number 
or whatever the user wants. A second dbf contains one record for every 
printjob holding the 3 project files from L&L, creation date and time of 
the printjob, username of the job creator, number of pages to print and 
- if necessary while printing, the position of a printstop inbetween. So 
I can start and stop and restart thes printjobs at any time and at any 
position, manually or automatically after maybee a certain number of 
pages. Also I have the possibility to first print into preview or 
directly to the printer.
And even if the origional L&L file has been modified inbetween the 
printjob is not affected because the L&Lfiles are stored in the job in 
that state as they had been when the printjob has been created. But I 
have optionally the possibility to restart the job with the later 
modified L&L-files or even attach a different L&L-file to the job, 
either temporary or for ever (than stored in the job replacing the 
previous stored L&L-files).
So I can for example with the same job first print hundreds of invoices 
and than attach a list project and print a list of names and sums of 
those invoices.
If the print job is not needed anymore the user can delete it.
Klemens