Linking Multiple Dbs (One From A Trigger, One Static Csv)
I have a label that currently is printed via a dropfile. The drop file specifies that it is to be used as the database connection for the label (using the /D CLI option). This process has worked wonderfully for well over a year.
The problem we have now is that I need to tie some additional information coming from an entirely separate system into these label prints. This data will live in a single CSV file that will be updated daily. Its not possible to merge this data into the system that generates the dropfile.
So ultimately what I need is this ... a way to have the dropfile still be used for the 98% of data coming out of the primary business system, but to have a static CSV file on the D:\ drive of my server used for the other 2% coming from the supplemental system.
Is this possible? Thanks for your advice.
The problem we have now is that I need to tie some additional information coming from an entirely separate system into these label prints. This data will live in a single CSV file that will be updated daily. Its not possible to merge this data into the system that generates the dropfile.
So ultimately what I need is this ... a way to have the dropfile still be used for the 98% of data coming out of the primary business system, but to have a static CSV file on the D:\ drive of my server used for the other 2% coming from the supplemental system.
Is this possible? Thanks for your advice.
0
-
This can certainly be done with BarTender and Commander
You would need to create a joined database directly on BarTender using the CSV file and the text file as separate data sources. Note that in this case, both databases will need to have a common field with the same data to be able to stablish its relationship.
As both database are connected through a text file database type connection you'll need to specify first the "fixed" database (in your case the CSV file) and secondly the variable one going to be substituted by the incoming trigger file (most of the time BarTender substitutes the second database if they are both text types, please test this before implementing it). Another possibility would be to use as "fixed" database another type of database (such as MS Access) in which case Commander will always substitute the text file connected regardless of its position.
Another thing to consider, only if you are using Commander script, is to remove the /R command from the trigger file as it's not needed when using a joined database (actually it will generate a "record not found" error and won't print).
Test it first printing directly from BarTender, and once it's running correctly, try printing from Commander; it will substitute the original text file (second text file on the "File>Database Connection Setup..." option) with the incoming trigger file.0 -
Corporate put a /R=3 into my drop files (even tho they contain a single record). I removed that from my testing files and things are working better. Thanks! 0
Iniciar sesión para dejar un comentario.
Comentarios
2 comentarios