Importing Data With Non-Access Naming Conventions

[Guest]

I am importing an xml document into Access 2003. The only problem is the xml
document (which is actually an Adobe Premiere project, if anyone is familiar
with those) uses naming conventions for fields that Access doesn't like -
e.g. "AudioSettings.Compile".

Is there any way around this? At present, I am importing only the tables of
the xml schema that I need into an Excel spreadsheet, and then linking the
table in the Access database, but I would much rather be able to import all
the tables into the database from within Access.

 

[John Vinson]

I am importing an xml document into Access 2003. The only problem is the xml
document (which is actually an Adobe Premiere project, if anyone is familiar
with those) uses naming conventions for fields that Access doesn't like -
e.g. "AudioSettings.Compile".

Is there any way around this? At present, I am importing only the tables of
the xml schema that I need into an Excel spreadsheet, and then linking the
table in the Access database, but I would much rather be able to import all
the tables into the database from within Access.

Is there some way you can force adobe to bracket the fieldnames? It's
a Bad Idea to have periods in fieldnames, since the period is a key
delimiter, but you *should* be able to get away with a field named

[Audiosettings.Compile]

provided you shield it with square brackets.

If you can *link* to the xml, you might want to consider creating your
tables with valid fieldnames, and running Append queries to migrate
the data from XML into Access.

John W. Vinson[MVP]