Why won't this update statement work?

Ruslan Zasukhin sunshine at public.kherson.ua
Sat Mar 13 21:55:04 CST 2004


On 3/13/04 9:51 PM, "Kristafer Vale" <kristafer at comcast.net> wrote:

> I don't have either of those two things available, but I have been able to
> narrow it down to one interesting/annoying fact. If there is a call like
> this:
> 
> set query = "select ID, slideShowID, title, filename, artist, SlideOrder
> from slides WHERE slideShowID like '\A"&gCurrentSlideShowID&"\Z' order by
> SlideOrder"
> 
> set mySlidesCursor = new( xtra "VCursor", getRef(gMyLessonDB), query)
> 
> in the same handler as this:
> 
> SqlExecute( gMyLessonDB, "DELETE FROM slides")
> 
> Then the SqlExecute command never fires. If I I move the sqlExecute it's own
> handler separate from the vCursor handler then it works as expected. Why
> would that be the case? Can we not mix a call to the database using  vCursor
> in the same handler as a SqlExecute command?

This is simple.

You cursor LOCK records.

So of course, the next DELETE command cannot delete them.


-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------



More information about the Valentina mailing list