Different Query Results On One Label
I saw the topic "Three different query results on one label" from 2012
Is this now possible with the newest version of BarTender?
-
Do you have a link to the topic in question?
Can you describe in detail what it is that you're wanting.
I don't think much different has happened in this area of BarTender within the last couple of years, and so it's likely that the same situation still holds true.
0 -
Here is the link
We would like to print a protocol. This protocol should contain data from multiple articles in our database. This means a collection of a main article and some sub articles, all with serialnumbers.All these database entries are reachable with one ID (Key), but i will get one entry for each main article / sub articleID - ArticleNo - SerialNo - Typ10 - 123.1234 - 123456789 - Maintype10 - 123.4444 - 154645644 - Subtype 110 - 123.6666 - 345834543 - Subtype 210 - 123.9999 - 7868768656 - Subtype 30 -
Unfortunately the situation is still the same. BarTender can only use a single database record maximum per label from its main database connection. There are workarounds such as with embedded VBScript or an application controlling BarTender via automation, but this is not possible using the default operation of the software.
0 -
Sorry to revive an old post, but could anyone direct me to info about the workarounds mentioned above?
0 -
BarTender's fundamental use of a database requires one record per label. However, in v10.1 there is a feature called the "Page Template" which serves as a workaround for allowing multiple records per label. I recommend looking into this feature to see if it will suit your needs.
You can find information on it in the following white paper:
http://www.seagullscientific.com/label-software/whitepapers/whitepaper_whatsnewinbt101.pdf
0 -
You also have the option that I begrudgingly prefer: Query your data in a way that returns 1:1 (record:label), ALL of the data you actually want.
This will require an ugly kludge to "pivot" the rowset to columns.
Of course, if you understand what I mean, you can clearly see that the larger the rowset that you're working with, this workaround becomes less of a kludge and more of an absolute impossibility.
I've managed to create 8x11 bills of lading and pack slips this way, but it requires a lot of SQL scripting, and many hours laying out all the fields in BT.
In the end though, no other methods I've seen work very well (or even acceptably) compared to this method for extremely complex formats.
0
请先登录再写评论。
评论
6 条评论