Ok, I figured out why this is happening, but not sure how to fix it. It turns out it's not a database problem afterall. What's happening is that I have the user select an item from a text-list. Then the can "delete" that item. It doesn't really delete it, just marks it not to be shown in the database. Anyway, the problem is that once a user does the delete, if they choose another item from the list to delete, it appears that the old index for the list is still in effect. So when they delete it, they are actually re-deleting the first one, which in effect does nothing. Any ideas on this?
>From: "Matt MacDonald" <[EMAIL PROTECTED]> >Reply-To: [EMAIL PROTECTED] >To: [EMAIL PROTECTED] >Subject: [REBOL] Multiple Database Updates >Date: Tue, 30 Sep 2003 09:13:29 -0400 > > >Does anybody know why this would be happening? > >I'm making a messaging client that reads messages from a SQL-Server using >the ODBC dataports in REBOL/Command. When I try to do sequential updates, >only the first one usually processes, the rest remain unchanged. Any >thoughts? > >Matt > >_________________________________________________________________ >Instant message in style with MSN Messenger 6.0. Download it now FREE! >http://msnmessenger-download.com > >-- >To unsubscribe from this list, just send an email to >[EMAIL PROTECTED] with unsubscribe as the subject. > _________________________________________________________________ Get MSN 8 Dial-up Internet Service FREE for one month. Limited time offer-- sign up now! http://join.msn.com/?page=dept/dialup -- To unsubscribe from this list, just send an email to [EMAIL PROTECTED] with unsubscribe as the subject.
