A New Label Design Crashes And Corrupts Bartender S’abonner

0
Avatar
Legacy Poster

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.

 

Questions:

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.

 

9 commentaires

0
Avatar
Levi Hargrove
Modérateur
Actions pour les commentaires Permalien

Hi there,

 

This sounds like a fairly severe instance of a bad installation. I cannot say what initially corrupted the label, or the installation, but it is possible to virtually wipe clean and start over. Also there's a good chance you're suffering from multiple issues, you very well may have corrupted printer driver as well. To answer some of your questions:

 

1) Yes there is, I would recommend a full reinstallation, which include registry values and program data removal. Please contact our support office for this, they will be happy to help with it.

2)Chances are you are not exceeding, or even getting near the limitations of the software, so I would rule this out with confidence.

3)Hopefully once the crashing is fixed you will not have to worry about more complex situations on the label. 

4)No.

5)No, not by any means is this necessary.

5b)The .NET API is not very crashy by any means, it's actually quite stable and used by a lot of people (when installations aren't corrupted)

 

I would recommend that you give your regional support office a call and see what they can do for you.This is the information regarding the support office hours and contact: http://www.seagullscientific.com/label-software/technical-support.aspx. 

 

As a side note, the BarTender labeling software is a very widely used program; some of the biggest names and biggest companies use this software. I can say with certainty that the product is stable, and in most cases received very well by customers. In this case, I believe it to be specific to your environment. 

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Thank you, very much, for the swift reply.

 

We ourselves have been using Bartender with great success for several years now.

 

Only on this particular label template have any instability issues arisen; I wasn't sure if they were doing so because this is our first use of complex barcode, data matrix, and quite so many named fields.

 

Again, thank you. My slowly growing concern over the long-term viability of our very complex and expensive label is successfully mitigated.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Unfortunately...

 

After cleaning out Seagull Scientific, Bartend, and Maestro related drivers files and registry entries, the label template opened, and the toolbars were uncorrupt.

 

However, after working for another 20 minutes designing the label, it crashed.  The "autosaved" version of the label, when opened, crashes BarTender instantly.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Maybe this would help tech support troubleshoot, the original file doesn't crash on me (10.1 SR4) but the format is dramatically less laggy when I remove the "Use VB Scripting" transform from the DataMatrix Human Readable that it's in now.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Thank you for the suggestion, nRyder.

 

Unfortunately, unchecking the Use VBScript option of the text under the Data Matrix did not improve the symptom, which was randomly choosing between crashing (APPCRASH) and simply hiding the menu and some of the toolbars.

 

Deleting the Data Matrix does fix it, so I looked deeper.

 

Two of the component data sources for the Data Matrix had VB transforms, so I unchecked the option, but the symptom remained.  So I re-enabled scripting option from the first field (with the date codes), deleted the script entirely from the dialog, and closed it. Then I tried to do the same to the other field, and BarTender crashed again.

 

So, thank you: something related to the Data Matrix itself appears to be the issue.  I will recreate it.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Well, I simplified the data matrix (it was pretty complex) by removing all scripting, prefix/postfix, search/replace, serialization. No change in symptom.

 

Then I simplified it by removing data sources entirely, both singly and in related groups, until it had zero data sources. No change in symptom.

 

Then I simplified it by setting every property I could find back to defaults. No luck.

 

I then changed it to a non-data matrix barcode. Works great.

Change it back to data matrix, symptom reappears.

 

Create a new document, drop in a data matrix, symptom appears.

 

Please advise. 

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

We are running Bartender Enterprise Automation v10.1 SR4 Build 2961 running on Windows 7 desktops.  We are able to create, modify and open all of our templates.  Now when any user attempts to open any of our label templates Bartender consistently crashes.  We have uninstalled the software, re-intalled the software and we still have the same exact issue.

 

What on earth could be the cause for this all of a sudden to start happening?  Absolutely nothing has changed as some of the templates that we are attempting to open have been in place for close to 5 years without any modifications to them at all.

 

Please advise

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

We have had same issues with Bartender 10.1 SR4 rolled back to SR3 build 2954 and all of our crashing with Datamatrix barcodes is resolved.

0
Avatar
Legacy Poster
Actions pour les commentaires Permalien

Just in case someone else has this issue.  If the last time you were in Bartender you had the LAYERS toolbar turned on.  You may have issues opening a template that has a Datamatrix label.  

 

To correct, open up a label that does not contain a Datamatrix barcode (or create a new label).  Go to VIEW, TOOLBOX, and un-check the LAYERS selection.  

 

The Seagull help person said that this was an issue that is being worked on.

 

This worked for me, hopefully it will work for others.

Vous devez vous connecter pour laisser un commentaire.