<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Invalid Field Name on Import from mySQL ODBC Connection: Error Code 0X80040204 in ArcGIS Pro Questions</title>
    <link>https://community.esri.com/t5/arcgis-pro-questions/invalid-field-name-on-import-from-mysql-odbc/m-p/1254158#M64983</link>
    <description>&lt;P&gt;Neil:&lt;/P&gt;&lt;P&gt;Had you ever tried this type of connection to MySQL in ArcMap?&lt;/P&gt;&lt;P&gt;I have been using an OLEDB (ODBC) connection to MySQL in ArcMap for years, but the same setup with a 64-bit connection is throwing errors in Pro when trying to access the exact same database tables.&lt;/P&gt;</description>
    <pubDate>Thu, 02 Feb 2023 00:04:13 GMT</pubDate>
    <dc:creator>MichaelVolz</dc:creator>
    <dc:date>2023-02-02T00:04:13Z</dc:date>
    <item>
      <title>Invalid Field Name on Import from mySQL ODBC Connection: Error Code 0X80040204</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/invalid-field-name-on-import-from-mysql-odbc/m-p/1245479#M63974</link>
      <description>&lt;P&gt;Receiving Error Code&amp;nbsp;0X80040204: "an Invalid field name was used in query string" when attempting to view attribute table of table imported from Database connection.&amp;nbsp;&lt;/P&gt;&lt;P&gt;No field names start with numbers or spaces or special characters. Field names only have letters, numbers, and underscores&lt;/P&gt;&lt;P&gt;When we limit the number of fields from ~45 to 5 it works no problem.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jan 2023 23:13:04 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/invalid-field-name-on-import-from-mysql-odbc/m-p/1245479#M63974</guid>
      <dc:creator>NeilHubbert</dc:creator>
      <dc:date>2023-01-04T23:13:04Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid Field Name on Import from mySQL ODBC Connection: Error Code 0X80040204</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/invalid-field-name-on-import-from-mysql-odbc/m-p/1246342#M64083</link>
      <description>&lt;P&gt;Is it possible one of your field names is a reserved word?&amp;nbsp; Each DBS has there own set of reserved words.&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://dev.mysql.com/doc/refman/8.0/en/keywords.html" target="_self"&gt;MySQL Reserved Words&lt;/A&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://support.esri.com/en/technical-article/000010906" target="_self"&gt;ESRI File Geodatabase Reserved Words&lt;/A&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://learn.microsoft.com/en-us/sql/t-sql/language-elements/reserved-keywords-transact-sql?redirectedfrom=MSDN&amp;amp;view=sql-server-ver16" target="_self"&gt;MS SQL Reserved Words&lt;/A&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://docs.oracle.com/cd/A97630_01/appdev.920/a42525/apb.htm" target="_self"&gt;ORACLE Reserved Words&lt;/A&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://www.postgresql.org/docs/current/sql-keywords-appendix.html" target="_self"&gt;PostgreSQL Reserved Words&lt;/A&gt;&lt;/P&gt;&lt;P class="lia-indent-padding-left-30px"&gt;&lt;A href="https://learn.microsoft.com/en-us/office/troubleshoot/access/reserved-words" target="_self"&gt;MS Access Reserved Words&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Also make sure none of your field names start with an underscore.&amp;nbsp; I was not aware of that one until recently.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="LanceCole_0-1673221862894.png" style="width: 608px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/59940i2FEF1EB32DE517CA/image-dimensions/608x359?v=v2" width="608" height="359" role="button" title="LanceCole_0-1673221862894.png" alt="LanceCole_0-1673221862894.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;You note 5 fields of ~45 work, try groups of fields until you get an error.&amp;nbsp; Then look for possible issues in that group.&amp;nbsp; Note, there may be more than one field that has an issue.&amp;nbsp; If you can post a list of the ~45 fields it, may be helpful for for someone to review them.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2023 00:11:14 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/invalid-field-name-on-import-from-mysql-odbc/m-p/1246342#M64083</guid>
      <dc:creator>LanceCole</dc:creator>
      <dc:date>2023-01-09T00:11:14Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid Field Name on Import from mySQL ODBC Connection: Error Code 0X80040204</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/invalid-field-name-on-import-from-mysql-odbc/m-p/1246648#M64100</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/201429"&gt;@LanceCole&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The problem (we think) has to do with one of our fields using the TIME datatype. Once those fields were removed, I was able to import the data fine. When those fields had their datatype changed to VARCHAR it also worked. The TIME format in our MySQL instance is the standard HH:MM:SS and the variable naming convention doesn't appear to be the issue either. Is there some nuance to converting the MySQL TIME datatype to something ESRI can use?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Jan 2023 23:52:02 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/invalid-field-name-on-import-from-mysql-odbc/m-p/1246648#M64100</guid>
      <dc:creator>NeilHubbert</dc:creator>
      <dc:date>2023-01-09T23:52:02Z</dc:date>
    </item>
    <item>
      <title>Re: Invalid Field Name on Import from mySQL ODBC Connection: Error Code 0X80040204</title>
      <link>https://community.esri.com/t5/arcgis-pro-questions/invalid-field-name-on-import-from-mysql-odbc/m-p/1254158#M64983</link>
      <description>&lt;P&gt;Neil:&lt;/P&gt;&lt;P&gt;Had you ever tried this type of connection to MySQL in ArcMap?&lt;/P&gt;&lt;P&gt;I have been using an OLEDB (ODBC) connection to MySQL in ArcMap for years, but the same setup with a 64-bit connection is throwing errors in Pro when trying to access the exact same database tables.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Feb 2023 00:04:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-pro-questions/invalid-field-name-on-import-from-mysql-odbc/m-p/1254158#M64983</guid>
      <dc:creator>MichaelVolz</dc:creator>
      <dc:date>2023-02-02T00:04:13Z</dc:date>
    </item>
  </channel>
</rss>

