[AccessD] XML Import - successful!!!!

The other thing we run into is when we tell it to ignoreschema instead of inferschema.  Access has major objections to objects named with reserved words, and its reserved words are somewhat different from SQL Server's.  We try to avoid both, but we can control the XML structure, so it's easier.

Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Greg Smith
Sent: Tuesday, December 05, 2006 1:46 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] XML Import - successful!!!!




Charlotte:

If the brackets you used work, and my changing the name to something else works, then either way I've got to modify the incoming XML file internally (either with brackets or a name change).  But that might explain better why it's doing that...makes more sense that it's an oddity than me just hitting a reserved word....?

Thanks.  Greg

===============================================

I've seen this kind of thing in .Net working with XML files. It doesn't


throw an error, it just can't fill the stream object with any data, so 

nothing is imported. Putting square brackets around the offending word 

in the xml might work. We've done that with some success. 



Charlotte Foust 




--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com