Same Column Name But Different Tables
I have designed a label. This label uses 2 Tables in total. There is 1 column name that is in both tables, but have different meanings. Both columns are on the label. When I BROWSE under the Database Connection tab, I can see both of those columns and their values... which are correct. However, when I print the label, both columns give the same value.
For Example: I have 2 Tables .. Invoice table, and Customer Alias table. In both tables there is a column name "AliasItemNo". In the Invoice Table, the AliasItemNo is 1234. In the CustomerAlias table the value of AliasItemNo is AC123. When I am under Browse in Data Connection setup, it shows two fields AliasItemNo and under each, shows the correct value. On the label, however, both fields show 1234 even though the Database table and column on the label is different.
Any ideas on how to fix this? I am using Bartender 9.4 R3
I think the label just uses the column name without referencing the Table it came from.. so would renaming one of the columns correct it's confusion and if so, how do I rename it within the custom SQL statement?
Thanks...
Kerry
For Example: I have 2 Tables .. Invoice table, and Customer Alias table. In both tables there is a column name "AliasItemNo". In the Invoice Table, the AliasItemNo is 1234. In the CustomerAlias table the value of AliasItemNo is AC123. When I am under Browse in Data Connection setup, it shows two fields AliasItemNo and under each, shows the correct value. On the label, however, both fields show 1234 even though the Database table and column on the label is different.
Any ideas on how to fix this? I am using Bartender 9.4 R3
I think the label just uses the column name without referencing the Table it came from.. so would renaming one of the columns correct it's confusion and if so, how do I rename it within the custom SQL statement?
Thanks...
Kerry
0
-
Hello Kerry,
You mention that you're connecting to two tables. In BarTender's database connection setup dialog you need to connect to tables / databases which are related (at least by one field). Which field(s) from each table have you used for joining both tables together? If you've used "AliasItemNo" for the join, then this would be why you're getting this behaviour.0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
1 Kommentar