Data Type Changes Back To Character
We have linked a datasource (CSV file) to our templates. In the Database Connection Setup we have changed some of the fields from the default Character Data Type to Integer - we then Save and Check In the template. When we later return to that template the Data Type for our fields has reverted back to Character??
Has anyone else seen this issue? Any recommendations on fixing it?
-
Hello Simon,
I've been trying to reproduce your issue but the documents I create connected to a CSV file maintain the changed data type.
1. Could you let me know what exact version, edition and build of BarTender are you working with?
2. A workaround could be to leave the field as the default type, but when loading its information to a BarTender data source, make sure that data source specifying the type of data (from the "Data Type" tap when selecting the actual data source in the object's properties).
In any case, why exactly do you need to specify the data type of the field? Are you performing some sort of arithmetic calculation? Are you using VB script for it?
Cheers.
0 -
Hi Fernando,
Thanks for your response.
Our BarTender version is as follows:
BarTender Version Enterprise Automation 10.1 Build 2926Operating System Windows Server 2008 R2 Standard [x64] SP 1
Database MS SQL 2012
We are using the data type to conditionally print layers in the label - I've attached one of the templates that have this issue. We're not using VB script just the standard Layer Properties --> Print Options --> Print Visibility settings.The technical support team in Asia Pacific have recommended upgrading to SR1 of 10.1 - do you agree that this would help?[attachment=635:BTTXT1.txt][attachment=636:3255__GIL_A4_SPECIAL__FOR_$_.btw][attachment=636:3255__GIL_A4_SPECIAL__FOR_$_.btw]
Regards,
Simon
0 -
Hello Simon,
Upgrading to v10.1 SR1 should certainly be your first step; at least so we can test in the same environment. Note that I'm are working with SR1 and still haven't been able to reproduce your issue even with your documents.
Another possibility that might be forcing the field definition to revert to "Char" is that you've specified one record to have a value of "xxxx.." on all fields, which cannot be recognize by "Integer" type. If you make sure that all fields are of a numeric value recognizable by the Integer type, do you still get this same issue?
Cheers.
0 -
Hi,
We upgraded to 10.1 SR1 but the problem is still there. We can now reproduce the error - follow the steps in the attached Data Type Issue PDF.
Regards,
Simon
0 -
Hello Simon,
I've tested your files and following your procedure I can certainly reproduce your issue. With that I can confirm that the cause is the extra records with "xxxx" values on it.
I modified your database text file removing this extra record and the field type of your fields won't change anymore.
Please understand that if you specify a field to be of the "Integer" type it cannot contain non-integer values such as the "x" character, or it will revert to a plausible field type (such as char). When you where changing the field from the data source it forced BarTender to scan the database (probably the first few records) and thus modified accordingly the type of those fields with incompatible values.
Cheers.
0 -
Thanks Fernando - this is fantastic! The problem does indeed go away.
Cheers,
Simon
0 -
Hi,
Unfortunately this problem has reappeared. I have checked the text file being used for the database connection setup and I'm sure there are no characters populated in non-character fields. I have attached a detailed description of how to replicate the error - can you suggest a resolution please?
Regards,
Simon
0 -
Hello Simon,
Thanks for your comment.
I've also been able to reproduce your issue with your files and with my own simpler ones. I've forwarded your issue to our development department, once they get back to me I'll comment their suggestions and ideas to the possible cause of this.
Thanks!
0 -
I hope this gets figured out soon as we are having the same issue with our system. since the column in question is used to join to a SQL database it is causing major headaches.
by removing the column header or making the header the same data type (int only) the issue seems to go away (so far anyway) but if you need the headers for identification, that is not very helpful.
-Andrew
0 -
Has there been any progress on this issue please?
0 -
Hello SimonD and Sournotes,
I wanted to let you know that our latest release for BarTender v10.1 (SR2), which includes the fix to this issue, is already available.
You'll be able to download it from the below webpage:
http://www.bartenderbarcodesoftware.com/label-software/barcode-label-printing-software-download.aspx
Regards.
0
请先登录再写评论。
评论
11 条评论