Altova Mailing List Archives>Archive Index >microsoft.public.xml Archive Home >Recent entries >Thread Prev - Exporting XML, editing to conform with existing schema [Thread Next] Re: Exporting XML, editing to conform with existing schemaTo: NULL Date: 1/3/2008 7:51:00 AM "Christopher M." <nospamcm_anon76@h...> wrote in message news:NhUej.4993$sE5.3528@trndny05... > I'm exporting XML from Access. There is an option to not export key and > index information to a schema (XSD) file, but there's no option for the > XML file. > > What I've been doing is using editors like AttEdit and XMLSpy to edit the > XML by removing the keys so it conforms to an existing schema. > > I'm having a problem though. I have a bunch of child elements, and I'm > trying to modify some elements of these child elements, but it seems that > I can only modify one child's child at a time. > > It seems like the only solution is to write some code to modify all of the > child elements or use Altova Mapforce. Or I guess I could try to modify my > tables in Access to eliminate the keys and use other fields instead, and > use where statements and cross joins instead of inner joins. Any ideas? > > > W. Pooh (AKA Winnie P.) > Sounds like the kind of thing XSLT is designed for. I've only used it once, and that was some time ago, so I can't provide specifics, but try searching for "XSLT" at Google or MSDN, -- Brendan Reynolds | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
