Increasing variable name size had a side effect

5 Posts
3 Users
0 Likes
33 Views
n.jayagobal
(@n-jayagobalarcinfo-com)
Posts: 45
Estimable Member
Topic starter
 

Increasing the variable name size had a side effect using ODBC driver.

PcVue version 11.1
Have developed with more than 40 character length tag names. All the functions are OK, except histroical database recording. We are using ODBC to mySQL database for third party access. While recording, we received error message as shown in the event viewer attachment and not writing the data to the table. We tried to change the table size to 80 and then 255, still it was not working. Kindly advice.

2210=317 ODBC1
2210=318 ODBC2
2210=319 ODBC3
 
Posted : 25/03/2015 9:02 am
e.mahaut
(@e-mahautarcinfo-com)
Posts: 270
Member Moderator
 

Hi Nagen,

Here is a French previous training module regarding PcVue 10.0 variable naming and archiving
Archivage ODBC
Les nouvelles limites ne sont pas supportées dans l’archivage des unités de type ODBC.
Le nom de la variable sera tronqué à 40 caractères.
Les attributs étendus seront tronqués à 40 caractères.
La description sera tronquée à 40 caractères.

In English:
ODBC archiving is not compatible with new naming limits.
Variable name, description and extended attributes are truncated if > 40 characters.

 
Posted : 25/03/2015 2:37 pm
n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
 

Hi Edouard,

May I know which training module you are talking about?

As you can see in the Nagen's screenshots the names are not truncated but errors raised!

I will check with Arnaud this point and probably make a SPR.

Nico

 
Posted : 27/03/2015 1:07 pm
e.mahaut
(@e-mahautarcinfo-com)
Posts: 270
Member Moderator
 

Hi Nico,

I remember with this post there was something written about it A long time ago in a galaxy far, far away.
I found it in a very old French training module, released 5 years ago.
Maybe things have changed (or not, or partially)

Edouard

 
Posted : 27/03/2015 2:46 pm
n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
 

Ok I checked with Arnaud.
Indeed you were right (as usual :whistle: ) the records must be done but truncated.
The anomaly is the CopyField error messages we can see in the logs.
I made a SPR (#60826) for that.

Thanks!

 
Posted : 27/03/2015 3:10 pm