cannot update cursor error...

Intermittently, I get an error "cannot update cursor" when trying to write
to a table. This table is opened at system startup, and gets read and
written to all day. It never gets closed, and it most certainly doesn't get
opened read only. But from time to time, this code:

select <mytable>
replace....

Generates error 111, cannot update cursor. I suspect something external,
though I really have no clue what. The code is clean and simple, and I can't
find a reason for this.

trw7at
Wed Dec 03 11:32:40 CST 2003

I'm sure this is unrelated, but you never know...

The only time I've seen this error is when I have a form
containing multiple listboxes or comboboxes with SQL SELECT
rowsources that are selecting INTO CURSOR and using the same
cursor. Might want to look around the data environment where
this takes place to see if you're using some other cursors
that are conflicting with the data update you're attempting.

-- TRW

Ook seemed to utter in news:ujrbQtBuDHA.1088@tk2msftngp13.phx.gbl:

> Intermittently, I get an error "cannot update cursor" when trying to
> write to a table. This table is opened at system startup, and gets read
> and written to all day. It never gets closed, and it most certainly
> doesn't get opened read only. But from time to time, this code:
>
> select <mytable>
> replace....
>
> Generates error 111, cannot update cursor. I suspect something
> external, though I really have no clue what. The code is clean and
> simple, and I can't find a reason for this.

--
_______________________________________
My e-mail: t r w 7
@ i x . n e t c o m . c o m
_______________________________________

Ook
Wed Dec 03 15:52:56 CST 2003

I looked at that - this app has no list boxes or comboboxes. The DE is
pretty clean, just a half dozen tables. The UI only has a few controls. It
happend twice, and has not happened since. The last time I has plagued with
weird problems like this, we moved the application to another box, and the
problem went away. Personally, I don't think it's the app or VFP - I've used
VFP and it's predecessors for 15 years, and I've never seen a table
mysteriously become read/write all by itself...it just doesn't happen...


"Tim Witort" <trw7at@ixdot.netcomdotcom> wrote in message
news:Xns94466127B9565timwitortwrotethis@207.217.77.206...
> I'm sure this is unrelated, but you never know...
>
> The only time I've seen this error is when I have a form
> containing multiple listboxes or comboboxes with SQL SELECT
> rowsources that are selecting INTO CURSOR and using the same
> cursor. Might want to look around the data environment where
> this takes place to see if you're using some other cursors
> that are conflicting with the data update you're attempting.
>
> -- TRW
>
> Ook seemed to utter in news:ujrbQtBuDHA.1088@tk2msftngp13.phx.gbl:
>
> > Intermittently, I get an error "cannot update cursor" when trying to
> > write to a table. This table is opened at system startup, and gets read
> > and written to all day. It never gets closed, and it most certainly
> > doesn't get opened read only. But from time to time, this code:
> >
> > select <mytable>
> > replace....
> >
> > Generates error 111, cannot update cursor. I suspect something
> > external, though I really have no clue what. The code is clean and
> > simple, and I can't find a reason for this.
>
> --
> _______________________________________
> My e-mail: t r w 7
> @ i x . n e t c o m . c o m
> _______________________________________