A New Label Design Crashes And Corrupts Bartender Follow
Hello, John here.
We're trying to design a new label, quite complex: it has about 20 separate face-slit labels per print-job all on a custom-designed roll of "meta-labels", and includes both Code 128 and Data Matrix barcodes, various images, and lots of text, taken from numerous named fields and a complex data entry dialog.
As I work on the new template design in Bartender, it keeps crashing on me. I am not making much progress.
This morning I was no longer able to open the last-saved version of the label template, as it immediately crashes Bartender. As does opening any "auto saved" document.
I was using 10.1SR3 (Automation). After checking for a new rev I updated to SR4: using the new version it crashed a few times trying to open the label template, but now it does open (nothing changed...). Unfortunately almost all the button-toolbars are simply missing, in both template and data entry design views.
1. Is there anything I can avoid doing to reduce the crashiness?
2. Are there limitations I might be exceeding that are increasing the crashiness?
3. As the template continues increasing in complexity am I going to suffer increasing crashiness?
4. We intend on implementing database access for this template, eventually. Is this a bad idea from the stability perspective?
5. I have a ton of work to go on the template before it is usable. Should I give up on Bartender and write a program to generate the label using the .NET API?
5b: how crashy is the .NET API?
6. Any additional suggestions would be most appreciated.
Thank you for your attention to this matter.
Please sign in to leave a comment.