I'm hoping to find some help and inspiration here :)
If this is not the right forum the friendly admin might please move this post accordingly. Thanks.
Please let me introduce shortly the current situation, and then my questions will follow below.
Thanks already for your support!
We are currently using a different Label software than Bartender.
We have quite a lot of different label designs with diffent values (mostly Names, MFD, EXPD, Serial Numbers (counters) with different Präfixes, Batch Numbers, some come with Data Matrix Codes (some of them GS1), Logo, Lines, Rectangles and such things).
We use a tiny bit of "database"(excel lists).
We also have some "standard" layout labels with an entry form.
Printing the labels is a manual job: opening up the label, entering the data, printing a number of 1-100 as needed. We have maybe 5-7 printing places with 10-15 printers, not everyone prints the same stuff.
The label files a stored in the company network (windows based).
I think a lot of you might recognise this situation.
I am now thinking of changing over to Bartender.
What I would love is to have all my different fields (like "Name" oder "SN" or "S/N" - yes, we have different designs for the same field on different labels :( ) in one database.
Then I would also like to somehow have the information about the layout for a certain label somehow stored (Database too?).
I would then like to have a prompt in Bartender asking the label ID, and then load up the layout with the fixed values for that label, and give me a prompt or form to enter things like start-serial number (with counter), manufacturing date etc.
Then how many of them, and off to the printer.
Is that a possible way? Or does "storing different layouts" means for me to just create the label in Bartender and insert fixed values and objects with database sources?
Is the whole prompting thing realistic?
Or - how would you tackle the problem we have (many labels with many layouts) in a freh and new setup??? I am open for suggestions!
Looking forward to your responses,
Please sign in to leave a comment.