Using ampersand (&) in the name of a Table Index hangs VCS 3.4.17 during Export #314
Comments
|
Interesting! I did some testing, and it looks like the underlying issue is that the native Microsoft Access By default Microsoft Access produces the following:
Technically, this is not valid XML. It fails an online validator, and triggers an error during the parse by the If you change
I will go ahead and add some VBA code to properly encode any ampersands that exist in the XML file, and also add some error handling to the XML parser so it will log an error and fall back to the original XML if something like this comes up in the future. Thanks again for reporting this! |
The XML output for a table def from Microsoft Access does not correctly encode the ampersand character. This creates XML that is technically invalid, and later fails to parse. #314
Added error handling to manage XML content that cannot be parsed. The raw XML will be dumped into the log file for further inspection. #314
The XML output for a table def from Microsoft Access does not correctly encode the ampersand character. This creates XML that is technically invalid, and later fails to parse. #314
|
Added fixes to the |
I found another edge case for HTML special entities where embedded quotes in the default value of a field were being sanitized incorrectly. #314
Discovered a scenario where an ampersand (&) was used in the Name of a Table Index and it was causing VCS 3.4.17 to hang during export.
The text was updated successfully, but these errors were encountered: