Csv Label Files And Sorting S’abonner

Legacy Poster

16 mai 2014 15:41

Our current warehouse-level retail control system exports a label file for each of our member stores in a standard CSV format. The export is generated as it goes through the UPC listing. Our existing label printing software that we are looking to replace has an option to sort the items imported form the CSV file into whatever order we need. I am testing the latest Enterprise Automation Trial (version 10.01 SR3) of Bartender on my local PC (Windows 7) to see if it will meet our needs. So far I am able to replicate our label formats and print the different forms and templates. The one issue I am currently having is figuring out how to achieve the final sorting. We normally sort the printed label output in numerical order by two of the fields inside the CSV (category and then warehouse item code). I cannot get this to work in Bartender. Any ideas?

6 commentaires

Legacy Poster

19 mai 2014 18:36

There is a "Sort" tab inside the database connection setup screen within BarTender. Does this have the functionality you're looking for?

Legacy Poster

19 mai 2014 19:59

I am not seeing the sort tab. On my "Database Connection Setup" I have the following tabs: Query, Options, Status, Browse. There is no sort showing up.

Legacy Poster

21 mai 2014 14:41

Well, you're right. I don't have a sort tab either when I import a .csv or .txt. When I import a .xls, it is there. I wonder why this is Seagull?

Domingo Rodriguez

Modérateur

22 mai 2014 10:02

Steven,

You can try to create an ODBC User DSN using the "Microsoft Access Text Driver" in ODBC Administrator, and then connect to this source from BarTender's database connection setup dialog. Do this by selecting "ODBC Data Source" and then your User DSN. Once connecting to the data source, you will see a "Sort" tab.

Legacy Poster

22 mai 2014 15:47

I don't think this will be a valid alternative. First, I am getting the "Failed to save table attributes of (null) into (null)" error from the Microsoft text driver bug when setting up the ODBC connection. I followed the suggestions on the MS support sites and edited the schema.ini manually to reset the garbaged field lengths to normal. This seems like a tenuous solution at best. Second, I am realizing that we will have to come up with a standard name for our label files in order to be able to use them in bartender. Right now we export 120+ files with a standard naming convention of LBL####.TXT where the #### is a location number. The fields embedded in the label template are locked to the database which is locked to the name which have to be rewritten when the database changes. What I was hoping would be a minor drop-in solution is turning into a major undertaking in completely redesigning all of our current process to conform to Bartender. I might have to step back and rethink this.

Legacy Poster

23 mai 2014 15:10

For your issue of naming the .txt file, the Commander utility actually has the ability to "Use Trigger File A Data File" or something like that. This means your .txt file could be any name and Commander will know to use that as the data when it triggers a print job.

Vous devez vous connecter pour laisser un commentaire.