Illegal Character in Library Fields

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Characters "ó" (Latin Small Letter O with Acute) or "Ó" (Latin Capital Letter O with Acute) are not allowed in library fields.
Other Polish diacritics are acceptable.

Footprint Expert 23 Enterprise Edition 23.11, 8/25/2023

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
tgrodnicki Members Profile Send Private Message Find Members Posts Add to Buddy List Advanced User Joined: 30 Sep 2014 Status: Offline Points: 106	Post Options Post Reply Quote tgrodnicki Report Post Thanks(0) Quote Reply Topic: Illegal Character in Library Fields Posted: 30 Aug 2023 at 5:51am
	Characters "ó" (Latin Small Letter O with Acute) or "Ó" (Latin Capital Letter O with Acute) are not allowed in library fields. Other Polish diacritics are acceptable. Footprint Expert 23 Enterprise Edition 23.11, 8/25/2023



Tom H Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 05 Jan 2012 Location: San Diego, CA Status: Offline Points: 5719	Post Options Post Reply Quote Tom H Report Post Thanks(1) Quote Reply Posted: 30 Aug 2023 at 7:49am
	The FPX file is ASCII format. Any "Symbol" is illegal in an ASCII database. People copy/paste data from a PDF file into a FPX cell and then the database becomes corrupt. You can open the FPX file in Excel spreadsheet and locate the damage easily and remove it. But to get the Excel data back to FPX you must copy/paste the Excel rows and columns into an ASCII text editor like Notepad and then save the file back to .fpx format. Common illegal Symbols are - ™ © ± ° µ ® € Ã
	Stay connected - follow us! X - LinkedIn

tgrodnicki Members Profile Send Private Message Find Members Posts Add to Buddy List Advanced User Joined: 30 Sep 2014 Status: Offline Points: 106	Post Options Post Reply Quote tgrodnicki Report Post Thanks(0) Quote Reply Posted: 30 Aug 2023 at 10:42pm
	I thought that since the 2020 database was accepting such characters, the current behavior was a bug. In this case, the program should not allow the input of characters with ASCII codes outside the range 20-127. If the database data format will be changed in the future, you can try to support Unicode encoding.

Jeff.M Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 16 May 2012 Location: San Diego Status: Offline Points: 477	Post Options Post Reply Quote Jeff.M Report Post Thanks(0) Quote Reply Posted: 27 Sep 2023 at 4:03pm
	Error checking added to library paste and edit operations that will flag and fix any illegal characters with ASCII codes of less than 32 or greater than 126.
	Stay connected - follow us! Twitter - LinkedIn

Tom H Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 05 Jan 2012 Location: San Diego, CA Status: Offline Points: 5719	Post Options Post Reply Quote Tom H Report Post Thanks(0) Quote Reply Posted: 28 Sep 2023 at 7:44am
	Download and install V23.13 to get this update - www.pcblibraries.com/downloads
	Stay connected - follow us! X - LinkedIn