K
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
T
Tom van Stiphout
On Wed, 3 Sep 2008 18:16:00 -0700, kq305
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
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
D
David W. Fenton
On Wed, 3 Sep 2008 18:16:00 -0700, kq305
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!
T
Tom van Stiphout
On 4 Sep 2008 21:43:00 GMT, "David W. Fenton"
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.
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.
D
David W. Fenton
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.