On Wed, 3 Sep 2008 18:16:00 -0700, kq305 wrote: I keep wondering about the details of the problem you are experiencing. Does it have anything to do with the Microsoft Access database system, the topic of this newsgroup? -Tom. Microsoft Access MVP
Tom van Stiphout wrote in news:9frub4l09sq5gkivotg0e8i8jhlp3j1mbd@4ax.com: > On Wed, 3 Sep 2008 18:16:00 -0700, kq305 > wrote: > > I keep wondering about the details of the problem you are > experiencing. > Does it have anything to do with the Microsoft Access database > system, the topic of this newsgroup? The error number is certainly not an Access error number! -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
On 4 Sep 2008 21:43:00 GMT, "David W. Fenton" <XXXusenet@dfenton.com.invalid> wrote: The error is likely from a COM component (I'm sure you have seen errors in the range 8000xxxx when working with ADO) so it COULD be relevant. More than likely the OP will not respond. Pretty typical for posts like this. -Tom. >Tom van Stiphout wrote in >news:9frub4l09sq5gkivotg0e8i8jhlp3j1mbd@4ax.com: > >> On Wed, 3 Sep 2008 18:16:00 -0700, kq305 >> wrote: >> >> I keep wondering about the details of the problem you are >> experiencing. >> Does it have anything to do with the Microsoft Access database >> system, the topic of this newsgroup? > >The error number is certainly not an Access error number!
Tom van Stiphout wrote in news:h3c1c4de7jdoitgc1ab4e2b3fp6ria98bg@4ax.com: > The error is likely from a COM component (I'm sure you have seen > errors in the range 8000xxxx when working with ADO) Well, no I haven't, since I've never once actually used ADO in a production app. -- David W. Fenton http://www.dfenton.com/ usenet at dfenton dot com http://www.dfenton.com/DFA/
