OK I'll give it a try. It shows up blank on my screen.

<?xml version = "1.0" encoding="Windows-1252" standalone="yes"?>
<xsd:schema id="VFPData" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
	<xsd:element name="VFPData" msdata:IsDataSet="true">
		<xsd:complexType>
			<xsd:choice maxOccurs="unbounded">
				<xsd:element name="tiphistory" minOccurs="0" maxOccurs="unbounded">
					<xsd:complexType>
						<xsd:sequence>
							<xsd:element name="tip_id">
								<xsd:simpleType>
									<xsd:restriction base="xsd:decimal">
										<xsd:totalDigits value="6"/>
										<xsd:fractionDigits value="2"/>
									</xsd:restriction>
								</xsd:simpleType>
							</xsd:element>
							<xsd:element name="history">
								<xsd:simpleType>
									<xsd:restriction base="xsd:string">
										<xsd:maxLength value="2147483647"/>
									</xsd:restriction>
								</xsd:simpleType>
							</xsd:element>
						</xsd:sequence>
					</xsd:complexType>
				</xsd:element>
			</xsd:choice>
			<xsd:anyAttribute namespace="http://www.w3.org/XML/1998/namespace" processContents="lax"/>
		</xsd:complexType>
	</xsd:element>
</xsd:schema>

I ran it through a validator and got the message -
---------------------------------------------------
XML Schema Validator

Well Formed: INVALID
Schema Validation: INCOMPLETE

The following errors were found:
TYPE LOC MESSAGE

Well Formed 69752, 37 An invalid XML character (Unicode: 0x2) was found in the element content of the document.
---------------------------------------------------
which suggests it has something to do with the encoding.
>I never had problem posting XML on UT between PRE tags
>
>>Also, while processing a different DBC it gives an error on one of the tables that says Access is having a problem processing the schema. I tried to post the schema here but it seems the code tags don't work with it. It is a simple table with only an integer field and a memo field. I can't figure what this one might be either.
>>