Linking to XML data - a step backwards

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi All,

So how do you link to XML data from Access? You Dont?

What about Access 2007? No good either!

Forgive me, but if Access and the like cant have a 2 way chat with the vast
amounts of XML data around arent we taking a major step backwards with XML?

I know all about transforming data (not my argument here) but we are losing
some major value. I just dont get the XML thing! And then theres the
relational aspect. Put your data in XML and lose major functionality - just
doesnt make sense.

Comments welcome around using the data rather than transforming it...
 
Hi, Tim.
So how do you link to XML data from Access? You Dont?
Click to expand...

Nope. Not without a driver for the XML file format, and because there is no
"standard" XML file format (it's defined within the file itself), there
probably isn't going to be a driver invented that will work on "any" XML
file.
Forgive me, but if Access and the like cant have a 2 way chat with the
vast
amounts of XML data around arent we taking a major step backwards with
XML?
Click to expand...

Access uses relational data structures, while XML is a hierarchical data
structure. These have to undergo conversion processes to be useful in the
other data structure.
I know all about transforming data (not my argument here) but we are
losing
some major value. I just dont get the XML thing!
Click to expand...

It's useful in quick data transfer with a customization capability to
identify what each data element is, regardless of what tool is being used to
transfer the data or what database type the data is being imported into or
exported from. Think of it as a fairly universal data transfer structure.
And then theres the
relational aspect. Put your data in XML and lose major functionality -
just
doesnt make sense.
Click to expand...

Once the data is transferred to its destination, one can do anything one
wants to do to it, such as relate it to other tables in a relational
database.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: http://DataDevilDog.BlogSpot.com http://DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
 
Thanks '69 Camaro for your considered reply and clear explanation. I must
leave behind my Access-coloured glasses!

Cheers

Tim
 
Hi, Tim.

You're welcome.
I must
leave behind my Access-coloured glasses!
Click to expand...

That's rather difficult, since Access makes using relational data so easy!
Using any other tool makes it seem harder than it needs to be.

Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blogs: www.DataDevilDog.BlogSpot.com, www.DatabaseTips.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.
 
So how do you link to XML data from Access? You Dont?

What about Access 2007? No good either!

Forgive me, but if Access and the like cant have a 2 way chat with
the vast amounts of XML data around arent we taking a major step
backwards with XML?

I know all about transforming data (not my argument here) but we
are losing some major value. I just dont get the XML thing! And
then theres the relational aspect. Put your data in XML and lose
major functionality - just doesnt make sense.

Comments welcome around using the data rather than transforming
it...
Click to expand...

From my point of view, XML is just the successor to CSV. Period.

And often, CSV is much easier and more efficient.
 
Back
Top