I'm using simple "SSELECT 'dict item(s)' TOXML ELEMENTS WITHDTD TO" 'file' statement to create the XML.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Alfke, Colin Sent: Thursday, September 09, 2004 1:09 PM To: [EMAIL PROTECTED] Subject: RE: [U2] ODBC driver for VSG (Visual Schema Generator) Unidata >-----Original Message----- >From: Craig Peterson [mailto:[EMAIL PROTECTED] >Sent: Thursday, September 09, 2004 8:09 AM >To: [EMAIL PROTECTED] >Subject: RE: [U2] ODBC driver for VSG (Visual Schema Generator) Unidata > > >Unidata Version 6.0 and UniData ODBC, Version 3.1.4. I had some trouble with some earlier drivers - but this should be OK. > >I can connect using Excel, haven't tried Access or others but will try >them in order to plead my case. > >Business Objects Data Integrator is an ETL tool. It has the ability to >Use XML file formats on import, which has been working fine with file >sizes under 100 Megabytes. I've been using XML, but thought I'd try >ODBC. I may need to explore UniOLEDB also. > Normally, we don't extract first. Maybe that's the difference? How are you doing the XML? There's a utility to build XML files with the cedarville Download program (ftp:\\ftp.cedarvill.edu that may not break down after 100 MB. Colin Alfke Calgary, AB ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
