Dean,
    Well, I wish I had the luxury of a real database, but unfortunately I'm
stuck using Microsoft Access.  I managed to get around the problem.  What I
was doing was using a command, setting the sql statment as the CommandText,
and then using "Set recordset = command.Execute" method.  However, I changed
to just a straight recordset, and it worked fine.  Thanks for the help
though!

James
----- Original Message -----
From: M. Dean Parkinson <deanparkinson@e...>
To: professional vb <pro_vb@p...>
Sent: Monday, June 19, 2000 11:38 AM
Subject: [pro_vb] RE: ADO error


> K - just read the original message again.  It is ADO.  I am assuming that
> you are using a real database like SQL Server or Oracle.  Look to see if
you
> are using a client-side or server-side cursor.  This was causing that
error
> for us a while back.
>
> Dean
>
> > -----Original Message-----
> > From: M. Dean Parkinson [mailto:deanparkinson@e...]
> > Sent: Monday, June 19, 2000 10:07 AM
> > To: professional vb
> > Subject: [pro_vb] RE: ADO error
> >
> >
> > James,
> >
> > Is it DAO or ADO?  If it is DAO then what are the parameters on your
> > OpenRecordset statement?  If the recordset is opened with
> > dbAppendOnly or if
> > it is opened with dbOpenForwardOnly and the table is empty then
> > you will get
> > this message.  It seems that I was also getting this error with an ADO
> > recordset but I can't remember all the circumstances.  I think it had
> > something to do with the connection being closed or something.
> >
> > I hope this helps.
> >
> > > -----Original Message-----
> > > From: texter@o... [mailto:texter@o...]
> > > Sent: Saturday, June 17, 2000 11:00 AM
> > > To: professional vb
> > > Subject: [pro_vb] ADO error
> > >
> > >
> > > I have a program that contains a recordset inside a code modual.  I
have
> > > set up my ADO code like I always do, except this time, anytime I
> > > try to do
> > > a MovePrevious or MoveFirst, I get the error "Operation Not
> > > Allowed In this
> > > context."  I can't figure out why I'm getting this error, when another
> > > program uses almost the same code, and it works just fine.  Any hints?
> > >
> > > James
> > >