nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Exporting to Excel, sometimes result can't import into Access?

cartographercartographer

Using the ArcGIS Desktop 10.4 Table to Excel Arctoolbox script in the Conversion Tools -> Excel I am sometimes able to make an Excel 97-2003 document that imports directly into Microsoft Access without any issues using the

DoCmd.TransferSpreadsheet acImport, acSpreadsheetTypeExcel8, "Table", strFilename, True

method, but sometimes it fails, and I have to open the document in Excel and save as a document of 97-2003 format with my Excel 2013.

Why does it not always work? Can null values in certain fields create a problem?

Trouver plus de publications taguées avec

Accepted answers

All comments

DanPatterson_Retired

Table To Excel—Help | ArcGIS for Desktop

Table To Excel is able to convert only to Microsoft Excel 5.0/95 Workbook (.xls) format.

Help indicates the export format.

cartographercartographer

Thank you. Now still trying to figure out how to import into Access 2013 without running into errors on occasion. Could null values or longer than 8 character field names with underscores make a difference?

DanPatterson_Retired

nulls must be known and accounted for, keep the field names short and underscores are fine

cartographercartographer

That almost answers my question. Does that mean Null values can make the import fail in Access?

And how short is short?

DanPatterson_Retired

Check Access requirements. Moving to arcmap to excel to access is going to be a good path to introduce problems. Why not find a format that arcmap and access can agree on without an intermediate excel stop ( ie like text or csv)

XanderBakker

Have you tried exporting the data to a personal geodatabase (this will yield an Access .mdb file).

Also when you export to Excel don't use the option "use field alias as column header" since this may produce invalid field names for the import to Access procedure.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.