🚀 go-pugleaf

I have search Microsoft site yesterday and have found nothing, maybe it's
ADOExpress...

The problem for me to pinpoint the problem is that I only have access to
Windows NT, ME and 95....
and as mentionned by you, it works....

But i'll try to find something in the borland site...

No users have reported that to me, but I won't take any chances and I will
change my code just to be sure ...

thanx steve....

bye!


SteveL <junk@essennell.co.uk> wrote in message
news:f2enut4cb0mnsj1jilf9bf0ajnp917oema@4ax.com...
> On Thu, 8 Nov 2001 16:19:53 -0500, "Rick Golden" <GoldenRick@hotmail.com>
> wrote:
>
> >Always be sure to close the recordset before.....
> >and you'll remove most of the errors.....
> >
> >maybe the error mentionned by Steve will still be there (haven't tried
it)
> >
>
> I'm closing the recordset after *every* op, so it isn't this (I connect to
> the DB only as and when reqd, because it's networked).
>
> I've changed the code to use a different TADOQuery object for updates, and
> it works great on MDAC 2.6* and 2.7. Do we think this is a bug in
ADOExpress
> under those environments? Or is this documented behaviour?
>
> Steve
> --
> mailto:steve.love@essennell.co.uk
> SMILE! And people will wonder
> what you're up to!
>
>      - ACCU -  accu.org -
> Professionalism in Programming
>