We have an ASP file written in VB script, which connects to Oracle via 
Microsoft OLEDB Provider for Oracle (Provider=MSDAORA.1).  

Set objCmd = Server.CreateObject("ADODB.Command")
Set objRs = Server.CreateObject("ADODB.RecordSet")

'Code here to asign connection string, parameters for Oracle stored 
procedure to objCmd

Set objRs = objCmd.Execute
Response.ContentType = "text/xml"
objRs.Save Response ,adPersistXML

The XML file has one of the data members like this (Oracle 10g):

<s:AttributeType name="G21" rs:number="21" rs:nullable="true" 
rs:writeunknown="true">
  <s:datatype dt:type="float" dt:maxLength="8" rs:precision="15" 
rs:fixedlength="true" /> 
  </s:AttributeType>

However, it retruned as below when Oracle was 9i:

<s:AttributeType name="G21" rs:number="21" rs:nullable="true" 
rs:writeunknown="true">
  <s:datatype dt:type="number" rs:dbtype="varnumeric" dt:maxLength="20" 
rs:scale="0" rs:precision="38" /> 
  </s:AttributeType>

There is no datatype and stored procedure change on Oracle side.  Why do we 
get diffrent datatype in ASP?  Is there any impact on data?  Is it possible 
to change the data attribute back to NUMBER in the ASP after the call to 
Oracle stored procedure?  If it is, how?