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 6:45:00 AM On Jan 2, 5:32=A0pm, "Christopher M." <nospamcm_ano...@hotmail.com> wrote: > 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 XM= L > file. > > What I've been doing is using editors like AttEdit andXMLSpyto 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 u= se > where statements and cross joins instead of inner joins. Any ideas? > > W. Pooh (AKA Winnie P.) Instead of writing a stylesheet if this is only a one-time occurence, Try using the Replace feature within XMLSpy under the edit Menu or the Ctrl+H hot key. Using MapForce will give you more control of the output. Jerry Sheehan http://www.altova.com | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
