To Mr. Lifesaver Bob,
Yes, I made it work with your xsd schema. But you successfully ignored my
questions, so that I can understand why there are such problems.
You underestimate the number of changes, but there are at least 7-8
small-to-major differences between the xsd file you have posted and the one
I had.
I compared everything in two columns of excel sheet, line by line ....yes
there are tons of differences. Everthing looks simple with this one small
file, but with so many nested xsd's I may be suicidal if I start modifying
files.
Have no idea what tool you used, "why" things are so screwy with XML
validity vs. flat files.
Still have no idea "WHY WHY WHY WHY" these vendors are spitting out xsd
files that are so useless and helpless with Microsoft's tools.
Simple example: you replaced the first two "integer" with "decimal", and
left the third one as "integer"
This is extremely weird.
http://www.w3.org/2001/XMLSchema">
minOccurs="1" maxOccurs="1" />
minOccurs="0" maxOccurs="1" />
minOccurs="0" maxOccurs="1" />
minOccurs="0" maxOccurs="1" />
minOccurs="1" maxOccurs="1" />
Lilya
+++++++++++++++++++++++++++++++++++
"Travis McGee"
hotmail.com> wrote in message news:...> Thanks Bob,
>
> I will experiment with this....but there are so many files to
> modify.....nearly impossible; and I am sure there will be lots of other
> glitches.
>
> What is the main source of the problem????!!!
> Standards issue? Version issue? Microsoft issue?
>
> Still does not understand, when SQLXML Bulk Load creates the table, how
> will it decide about the length of the
> type="xsd:string" /> for field. Usually the values will be truncated if
> it picks SQL Server default value, without looking at the entire xml data
> file. What am I missing here?
>
> Best Regards
> Lilya
>
>
> "Bob"
discussions.microsoft.com> wrote in message
> news:1934263D-E61D-40C3-8A1E-9D3FD32CE1FB@microsoft.com...>>I got this revised schema1.xsd to work:
>>
>> http://www.w3.org/2001/XMLSchema"
>> xmlns:sql="urn:schemas-microsoft-com:mapping-schema">
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> "Travis McGee" wrote:
>>
>>> "Travis McGee"
hotmail.com> wrote in message
>>> news:eLS4%%23jYAJHA.1228@TK2MSFTNGP02.phx.gbl...>>>>I am getting "relationship expected on" errors on SQLXML Loading Code
>>>>when
>>>>I
>>>> am creating the tables and then perhaps adding.inserting the data.
>>>>
>>>> Set oLoad = CreateObject("SQLXMLBulkLoad.SQLXMLBulkload.4.0")
>>>>
oLoad.ConnectionString = gsConn
>>>> oLoad.ErrorLogFile = "c:\error.log"
>>>> oLoad.SchemaGen = True
>>>> oLoad.SGDropTables = False
>>>> oLoad.BulkLoad = False
>>>> oLoad.Execute "c:\schema1.xsd" , "c:\data1.xml"
>>>>
>>>> These files came from outsitde- many of them; for the purpose of bulk
>>>> inserting into the database.
>>>> What is the problem? Missing Annotation? Is SQLXML too picky?
>>>> Why do we have to touch all of the Schema files? Are there two
>>>> different
>>>> standards?
>>>>
>>>> These are small files
>>>>
http://www.HumanGenome.org/data/schema1.xsd
>>>>
http://www.HumanGenome.org/data/data1.xml
>>>> is giving me....relationship expected on 'ING'
>>>>
>>>> and then
>>>>
http://www.HumanGenome.org/data/schema2.xsd
>>>>
http://www.HumanGenome.org/data/data2.xml
>>>> is giving me....relationship expected on 'COMBINATION_PACK_IND'
>>>>
>>>> This has something to do with missing annotation, I think.
>>>>
>>>> Can somebody help me
>>>>
>>>> Lilya Lopekha
>>>>
>>>
>>>
>>>
>
>
