seeCoolGuy wrote:

> I've been using Access to import some data straight into a sql server
> database by simply importing the xml file.

I'm not sure what "simply importing the xml file." means.

Does Access expect to see XML here, and _treat_it_as_ XML ?
Or will it expect to see CDATA here, and will thus encode it so as to
be suitable for inclusion inside XML (as CDATA), i.e. it'll convert to
<

> it reads like the following
>
>   <TblPartDesriptions_to_translate>
>     <intpartid>79</intpartid>
>     <strpartdescription>Part Description Here</strpartdescription>
>     <strlongdescription>some really long text here
> m<sup>3</sup>/min.)</strlongdescription>
>   </TblPartDesriptions_to_translate>

_Does_ it read like this? This is what you'd expect, and I'd expect
other tools to then process it corrrectly.

However I suspect that Access may have helpfully(sic) delivered you
this instead:
<strlongdescription>some really long text here
m&lt;sup&gt;3&lt;/sup&gt;/min.)</strlongdescription>


> any help is appreciated, perhaps a modified xsl file?

XSL is rarely any use for this sort of problem. What you need is a very
clear mental model of what's text (i.e. CDATA), what's XML, and to make
sure that exactly the right type and number of encodings is applied
when moving between each.