| colin.wiseman |
| Newbie |
|
|
|
|
| None Specified |
|
| Wednesday, December 5, 2007 |
| Wednesday, December 5, 2007 11:00:30 AM |
3
[0.02% of all post / 0.00 posts per day] |
|
Hi Christophe,
Ok i will give it a shot. Will let you know if i have success.
Cheers
Colin
|
|
Forget that last sentence. My bad, it was limited to 4 nodes deep...working now. But still need to comma seperate multiple nodes.
|
Thanks first of all for a great product. Used it a couple of times before and everything was spot on.
I have just been given a new XML document and i need to export the data to SQL Server, and then mash that data into a new format that the client has asked for...bit of a pain but hey ho its my job.
Everything seems to have worked with the database convert, there were no errors, however when i look at some of the tables it has flattened certain elements into 1 field.
Part of XML Document before convert...
<objectlist>
<object>
<cooking>
<cuisine>Sfd</cuisine>
<cuisine>Idn</cuisine>
<cuisine>Brit</cuisine>
<cuisine>Scsh</cuisine>
<cuisine>Itn</cuisine>
<cuisine>Mxn</cuisine>
<cuisine>Cajn</cuisine>
<cuisine>Gen</cuisine>
<cuisine>SrvF</cuisine>
<cuisine>Snk</cuisine>
</cooking>
</object>
<object />
.
.
.
<object />
</objectlist>
And there are other nodes that have similar structure. However when the convert does it's job, the out put looks like:
PrimaryKey ForiegnKey Cuisine
1 1 SfdIdnBritScshItnMxnCajnGenSrvFSnk
Is there any options (that are currently escaping me) to allow for comma seperation of these fields? Or even to have a seperate cuisine table that would reference cooking top level object with a foreign key?
Also some of the elements do not seem to be converted into fields. Is the 30day trial limited in someway?
|
|
