Date: Tue, 17 Jul 2007 17:07:15 -0600
Reply-To: Alan Churchill <savian001@GMAIL.COM>
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Alan Churchill <savian001@GMAIL.COM>
Subject: Re: Basic question, I hope...SAS XML too
In-Reply-To: <1184712753.562839.77750@m37g2000prh.googlegroups.com>
Content-Type: text/plain; charset="iso-8859-1"
David,
Good ideas.
Yes, I do need XML because I cannot write to a SAS dataset directly. XML
seemed like a good choice since it can have embedded metadata. However, the
lack of XSD support has kind of cramped that idea. Looking back, I could
have used CSVs and achieved a similar outcome but I was happy for the
experience...in a way...somewhat... ;-].
The app does already communicate using OleDb but for reading only. I do not
believe that you can write back to SAS using OleDb or ODBC (please correct
me if I am wrong here).
Regardless, I have it solved right now and have a dll for future use that
supports reading, writing, and updating of SAS datasets AND preservation of
all SAS metadata in and out. Plus a nice little XML Map writer so I don't
have to use XML Mapper (JEG) again...
Alan
Alan Churchill
Savian "Bridging SAS and Microsoft Technologies"
www.savian.net
-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of David
Sent: Tuesday, July 17, 2007 4:53 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: Basic question, I hope...SAS XML too
If your data is in a regular enough structure (rows and columns) to be
read in and out of a dataset, do you really need XML?
Could you avoid the libname engine entirely, use put statments to
write the data and call an XSLT engine to read/translate it?
Could you use SAS as a back-end only, have it act as a database, and
have your application communicate with SAS using ODBC or OLEDB? Then
you could forget about SAS's XML support entirely.
On Jul 12, 5:19 pm, savian...@GMAIL.COM (Alan Churchill) wrote:
> Is there a better way to accomplish this goal?
