View Issue Details

IDProjectCategoryView StatusLast Update
00032152 - Next Dev List (Holding Area)Bugpublic2019-06-15 11:36
ReporterK7ZCZAssigned ToK7ZCZ 
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Summary0003215: ALE handles international characters when editing, but not when adding records on SQL Server back-end
DescriptionPasting international characters into the ALE works, but the record saved garbles the strings. They don't successfully round-trip to the database.

This seems to work fine with Microsoft Access; it's just SQL Server that has trouble. (MySQL has trouble, too ... but detects the error and refuses the insert. See Mantis 1963)
Steps To Reproduce1) Fire up the logbook. Open any Access database.
2) Use the "+" button in the tool bar to open the ALE to add a record.
3) Enter any bogus call sign -- or, your own.
4) Wait for whatever call sign lookup you've got configured to execute.
5) Paste this text "鈴木 一朗" into the "Name" field. It is the name of a famous Japanese baseball player.
6) Paste this text "〒105-0011 東京都港区芝公園4丁目2−8" into the address field. It is the address of a landmark tower in Tokyo.
7) Press "Add" to add the record.
8) Close the ALE.
9) Double click the new record in the logbook view to edit it.


BUG#1) The "Name" field shows a bunch of question marks.

BUG#2) The "Address" field does, too.


10) Using Microsoft Access, open the database file that you chose in Step #1.
11) Review the record in the Access table editor. Note that the data is correctly landed in the fields.


10) In the editing ALE, paste the same strings again, erasing the question marks.
11) Press "Update" to save the changes.
12) Close the ALE.
13) Double-click the record in the logbook to edit it again

14) The strings are displayed correctly.
TagsNo tags attached.
ModuleLogbook
Sub-ModuleData
TestingNot Started

Relationships

related to 0003181 resolvedK7ZCZ Logbook requires a database schema migration solution 

Activities

K7ZCZ

2019-04-03 14:05

administrator   ~0007819

fixed with this checkin in the 6.7 branch:
https://hrdsoftware.visualstudio.com/HRD/_versionControl/changeset/4934

Issue History

Date Modified Username Field Change
2019-03-02 10:01 K7ZCZ New Issue
2019-03-02 10:03 K7ZCZ Summary ALE handles international characters when editing, but not when adding records => ALE handles international characters when editing, but not when adding records on SQL Server back-end
2019-03-02 10:03 K7ZCZ Description Updated View Revisions
2019-03-02 10:03 K7ZCZ Steps to Reproduce Updated View Revisions
2019-04-03 14:05 K7ZCZ Relationship added related to 0003181
2019-04-03 14:05 K7ZCZ Assigned To => K7ZCZ
2019-04-03 14:05 K7ZCZ Status new => resolved
2019-04-03 14:05 K7ZCZ Resolution open => fixed
2019-04-03 14:05 K7ZCZ Note Added: 0007819
2019-06-15 11:36 WA9PIE Project 3 - Current Dev List => 2 - Next Dev List (Holding Area)