Re: Persisting ADO as XML - almost convinced i'm crazy!
From: Douglas J. Steele (NOSPAM_djsteele_at_NOSPAM_canada.com)
Date: 12/22/04
- Next message: Tom Moreau: "Re: Persisting ADO as XML - almost convinced i'm crazy!"
- Previous message: John: "AppendChunk on image field"
- In reply to: Tom Moreau: "Re: Persisting ADO as XML - almost convinced i'm crazy!"
- Next in thread: Tom Moreau: "Re: Persisting ADO as XML - almost convinced i'm crazy!"
- Reply: Tom Moreau: "Re: Persisting ADO as XML - almost convinced i'm crazy!"
- Reply: Tom Moreau: "Re: Persisting ADO as XML - almost convinced i'm crazy!"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 21 Dec 2004 19:32:42 -0500
Using Option Explicit would have turned up an error.
Including adovbs.inc will give you the built-in constants.
-- Doug Steele, Microsoft Access MVP http://I.Am/DougSteele (no e-mails, please!) "Tom Moreau" <tom@dont.spam.me.cips.ca> wrote in message news:%23nc9em55EHA.2452@TK2MSFTNGP14.phx.gbl... > I really wish VBScript would be able to handle "built-in" constants. This > type of thing happens to me often enough. > > -- > Tom > > --------------------------------------------------------------- > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA > SQL Server MVP > Columnist, SQL Server Professional > Toronto, ON Canada > www.pinnaclepublishing.com > > > "Kelly C" <kelly.cromwell@synergisticbe.com> wrote in message > news:0h%xd.539297$Pl.535769@pd7tw1no... > Thanks, I guess I wasn't going crazy at all .... bah, stupid non standards > lol .. > > all hail .NET > > > "Tom Moreau" <tom@dont.spam.me.cips.ca> wrote in message > news:uS39$X55EHA.3120@TK2MSFTNGP12.phx.gbl... > > Try adding the following at the top of your code: > > > > Const adPersistXML = 1 > > > > -- > > Tom > > > > --------------------------------------------------------------- > > Thomas A. Moreau, BSc, PhD, MCSE, MCDBA > > SQL Server MVP > > Columnist, SQL Server Professional > > Toronto, ON Canada > > www.pinnaclepublishing.com > > > > > > "Kelly C" <kelly.cromwell@synergisticbe.com> wrote in message > > news:cYZxd.562280$%k.318934@pd7tw2no... > > Alright folks, this is something i've done a few times before, and I think > > i'm suffering from analysis paralysis ... so some fresh eyes' would be > > appreciated. What i'm trying to do is run a query, take the resulting > > ADO.Recordset and save it as an xml file. This is what i'm doing in an > asp > > file: > > > > strSQL = "SELECT * FROM TABLE" > > Set rsMyRecordset= Server.CreateObject("ADODB.Recordset") > > rsMyRecordset.Open strSQL, myConnection, adOpenStatic > > > > if rsMyRecordset.BOF and rsMyRecordset.EOF then > > Response.write("No RecordsFound.") > > else > > rsMyRecordset.Save "C:\test.xml", adPersistXML > > end if > > > > okay ... now basically what's happening is, i'm getting a test.xml file > that > > looks identical to the binary file I get when I drop the adPersistXML > > option. Am I forgetting something? Why won't it just save as text!!!??? > > > > > >
- Next message: Tom Moreau: "Re: Persisting ADO as XML - almost convinced i'm crazy!"
- Previous message: John: "AppendChunk on image field"
- In reply to: Tom Moreau: "Re: Persisting ADO as XML - almost convinced i'm crazy!"
- Next in thread: Tom Moreau: "Re: Persisting ADO as XML - almost convinced i'm crazy!"
- Reply: Tom Moreau: "Re: Persisting ADO as XML - almost convinced i'm crazy!"
- Reply: Tom Moreau: "Re: Persisting ADO as XML - almost convinced i'm crazy!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|