In the previous version of List&Label, LL29, I reported a bug that made that, in a project of type Label, the event that defines the variables (AutoDefineNewPage) was raised not only once per label but also once per page, which made the printing of the labels to be misaligned with respect to the source data.
This bug was fixed in a Prerelease Service Pack in May’24, which I installed and effectively solved the problem.
Now, after upgrading to version 30, I have found that this bug is happening again. Can you take a look at it?
Hi, I have just installed the latest Prerelase Service Pack (12/17/24).
I don’t know what has happened but now it won’t let me print any label.
When I execute TListLabel30.Print on any Label Project, it returns error -23 (One of the expression used has an error…).
These labels have worked correctly before until this latest patch, so I don’t think the problem is their design (the problem was the number of calls to AutoDefineNewPage, which left unprinted labels and repeated labels, but the data displayed in each label was processed correctly until today).
In fact, if instead of TListLabel30.Print I execute TListLabel30.Design, the Designer opens the label without any problem and without reporting any expression errors (it even lets me print it from its File menu), so I have no way to find out what is triggering the exception.
tmetternich
(combit Support - Thomas Metternich)
9
In our tests with the print method, we did not see the problem. Perhaps you can modify the FireDAC databinding example so that the problem can be reproduced here.
Maybe you can create a logfile with Debwin4.exe:
1.Exit your application.
2.Start the debugging tool “Debwin4.exe” from the List & Label installation directory (folder “Miscellaneous”).
3.In Debwin4, select “Capture List & Label Log”.
4.Now start your application.
5.Please repeat the steps until the error occurs again.
6.Save the log file in Debwin4 via “Save Log”.
I’d suggest to open a support case via our support center. Please copy any pertinent information from this thread into the case description and upload the logfile in the case.
In this case, the processing of the case would be free of charge.
After studying it further I found that the problem is that now the Print method does not call AutoDefineNewPage at all, so it does not define the variables and that’s why it gives error -23.
However, with the same code and the same label, the Design method does call AutoDefineNewPage correctly, and that’s why it doesn’t notify me of any error in the Designer to fix.
Please, can you check once more the calls to AutoDefineNewPage from Print in a Label Project?
If you consider it necessary I will open a support ticket as you suggested.
Thank you very much and sorry for the inconvenience.
tmetternich
(combit Support - Thomas Metternich)
11
I recommend that you open a support case here. I could not reproduce the behavior you described with the print method. We will therefore have to exchange more data.
Please try to change the databinding example so that the behavior occurs with the print method.
Please also upload the debwin log of your application to the case.
