xml into ado connectionless recordset
What's the path of least resistance for updating the database from an xml
dom object via an ADO 2.5 recordset? Saving it to a file and then reading
it into ado is not an option for this multi-user application.
I'd rather not have to loop through and pick from the DOM and put into a
record... ... ......
TIA
[348 byte] By [
Mark] at [2007-11-9 14:55:29]
# 1 Re: xml into ado connectionless recordset
Mark,
I might not be adding anything in this thread, it seems you have listed both
only possible solutions in the query itself!
It'll be a better idea to have the conversion utility as a COM class module,
which converts data to/from ADO/XMLDOM.
Moreover, you must be knowing, that for conversions through a disk file also,
you must have the xml data in MS-ADO standard format (to see the format,
save any opened recordset as xml).
(In case you opt to make this utility, i'll be interested in getting it,
if you don't mind. I'll be happy to get involved in any such design work
also.)
Bye
Rohit
(rohitw@futuresoftindia.com)
# 2 Re: xml into ado connectionless recordset
Tried like **** to make ADO 2.1 recordset to understand XML, doesn't look
possible without re-inventing the wheel again..
with ADO 2.5 also, as MSPersist, only provide XML in MS Specific (GRrrrrrrr)
format.
your idea is cool Rohit..
but a better way would be, to create a Provider
say.. DOJPersist .. LOL :-)
i.e. a Provider, which can take *OPEN* XML and provide in ADO Understandable
format.
flexibility comes with overheads.. man...
don't know much..will have to do some R&D.
keep me updated if you have anything on this topic.
will do the same.
"Rohit Wason" <rohitw@futuresoftindia.com> wrote:
>
>Mark,
>I might not be adding anything in this thread, it seems you have listed
both
>only possible solutions in the query itself!
>It'll be a better idea to have the conversion utility as a COM class module,
>which converts data to/from ADO/XMLDOM.
>
>Moreover, you must be knowing, that for conversions through a disk file
also,
>you must have the xml data in MS-ADO standard format (to see the format,
>save any opened recordset as xml).
>
>(In case you opt to make this utility, i'll be interested in getting it,
>if you don't mind. I'll be happy to get involved in any such design work
>also.)
>
>Bye
>Rohit
>(rohitw@futuresoftindia.com)
# 3 Re: xml into ado connectionless recordset
If your xml does not have standard MS format, try using XSL to transform what
you have to what MS wants. Only a suggestion, perhaps you have already tried
it.
"Sukhdev Singh Zala" <smzala@hotmail.com> wrote:
>
>Tried like **** to make ADO 2.1 recordset to understand XML, doesn't look
>possible without re-inventing the wheel again..
>
>with ADO 2.5 also, as MSPersist, only provide XML in MS Specific (GRrrrrrrr)
>format.
>
>your idea is cool Rohit..
>
>but a better way would be, to create a Provider
>say.. DOJPersist .. LOL :-)
>
>i.e. a Provider, which can take *OPEN* XML and provide in ADO Understandable
>format.
>
>flexibility comes with overheads.. man...
>
>don't know much..will have to do some R&D.
>
>keep me updated if you have anything on this topic.
>will do the same.
>
>
>"Rohit Wason" <rohitw@futuresoftindia.com> wrote:
>>
>>Mark,
>>I might not be adding anything in this thread, it seems you have listed
>both
>>only possible solutions in the query itself!
>>It'll be a better idea to have the conversion utility as a COM class module,
>>which converts data to/from ADO/XMLDOM.
>>
>>Moreover, you must be knowing, that for conversions through a disk file
>also,
>>you must have the xml data in MS-ADO standard format (to see the format,
>>save any opened recordset as xml).
>>
>>(In case you opt to make this utility, i'll be interested in getting it,
>>if you don't mind. I'll be happy to get involved in any such design work
>>also.)
>>
>>Bye
>>Rohit
>>(rohitw@futuresoftindia.com)
>
