Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!news.nobody.at!feeder.erje.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: The Dubious Khelair Newsgroups: comp.lang.basic.visual.database Subject: Re: ADODB.Recordset inaccessible Date: Fri, 16 Sep 2011 12:54:58 +0000 (UTC) Organization: A noiseless patient Spider Lines: 20 Message-ID: References: Injection-Date: Fri, 16 Sep 2011 12:54:58 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="QWiYPFFSlHAA+owAanbPVw"; logging-data="18401"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/fuqOAR5h2W1Pbrued+zz2oFoayFWHguU=" User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (OpenBSD/4.9 (i386)) Cancel-Lock: sha1:d9YYT+4Vz0IG8PsDDogiF5EoK2M= Xref: x330-a1.tempe.blueboxinc.net comp.lang.basic.visual.database:10 I was wrong. The ADODB.Recordset object is still not behaving at all. It is saying that it doesn't have the .rows or .fields property; auto-completion when I put in the '.' following the recordset object only fills it in with the usual suspects (ie ToString and the other 4 or 5). Anybody that might help would be much appreciated. The Dubious Khelair wrote: > Okay; as I figured it was a problem that is seeming pretty > foolish. I haven't been able to try this out yet, but I believe it > sounds like a pretty plausible solution. > I was under the mistaken impression that my ADODB.Recordset > object was going to slurp in the entire results of my query, and that I > could immediately close the ADODB.Connection object when I was done with > it, being able to later peruse the Recordset object at my leisure. I've > been informed that this is not the case, however. I'm not used to this > environment, though; that's really something that I should've tried when > debugging but I didn't even think about it.