Drpdown List Not Working
I have a Dropdown List filled from a VBScript reading a database that, when selected, sets a value in a Named Data Source. This Named Data Source is then used in VBScript to populate other template fields.
This works correctly in BarTender EA V10.1 SR4.
This has stopped working in BarTender 2016.
Today we upgraded to BarTender 2016 EA, fully licensed.
The Dropdown List control no longer sets the Named Data Source on selection, so labels are blank. If I redirect the Named Data Source to a simple text input field and enter the data value manually, it works. The label is properly populated.
I tried creating a new Dropdown, a new Named Data Source, populating the list with sample data at design time... None of these worked.
This problem exists on templates in both the 10.1 and 2016 template formats in the BarTender Designer.
Please advise.
-
In BarTender 2016 you can populate the list via a database data source. Why don't you use that? It all works fine for me. perhaps you attach an example label together with a text file to see what you might be doing wrong. Watch the following video:
https://www.youtube.com/watch?v=dCmAzvPgcnk0 -
I able to populate the Dropdown lists correctly, from embedded data, script (preferred method), database, and an external file.
I created text fields on the template to display the selected value.
Only data entered in a text field shows on the template. Any value selected in a dropdown does not show.
I have attached a stripped-down sample that reads from an external file. Data from the other controls appears , but not from the selected values.
0 -
Perhaps you should tell me where I should put files as your example runs script at every move I make in BarTender and then hangs for a while, I presume looking for the file, until control passes back again. I'm not sure why you feel VBS is the best way to fill the list, but I guess you have a reason. Anyhow, perhaps you've not properly linked the form control to an appropriate data source which is used in the template...
0 -
I spoke with someone at Technical Support on Wednesday. It seems our templates were corrupt. (Both templates were based on the same original file.)
I started from scratch with new template files and rebuilt element by element. One is fixed and working properly now, one to go. I'm just a little puzzled why it worked in v10.1 and not in 2016. Oh, well, moving on...
0
Please sign in to leave a comment.
Comments
4 comments