[AccessD] Intermittent #Deleted Records

Dan Waters dwaters at usinternet.com
Fri Mar 7 15:38:00 CST 2003


No, those are just data fields.

-----Original Message-----
From: accessd-admin at databaseadvisors.com
[mailto:accessd-admin at databaseadvisors.com] On Behalf Of Wortz, Charles
Sent: Friday, March 07, 2003 11:21 AM
To: accessd at databaseadvisors.com
Cc: Roni Ronyak
Subject: RE: [AccessD] Intermittent #Deleted Records



Dan, 

Is the information in the combobox that is getting changed either a PK
or a FK?  Better not be. 

Charles Wortz 
Software Development Division 
Texas Education Agency 
1701 N. Congress Ave 
Austin, TX 78701-1494 
512-463-9493 
CWortz at tea.state.tx.us 


 -----Original Message----- 
From:   accessd-admin at databaseadvisors.com [
<mailto:accessd-admin at databaseadvisors.com>
mailto:accessd-admin at databaseadvisors.com]  On Behalf Of Dan Waters 
Sent:   Friday 2003 Mar 07 11:09 
To:     accessd at databaseadvisors.com 
Cc:     'Roni Ronyak' 
Subject:        [AccessD] Intermittent #Deleted Records 

Folks, 

A database I have worked on has an intermittent problem.  This is a main
form and a subform in Access XP.  The database is split FE/BE.  The
subform is continuous and has a table as its recordsource that is on the
many side of a 1-many relationship with the table that is the record
source for the main form.  The database is set to individual record
locking and is also set to edited record.  The table for the subform is
also on the 1 side of a 1-many relationship for four other tables.
Every table has a primary key based on an autonumber, and that primary
key is the only index on each table.

The problem is that, sometimes, when someone changes existing
information in one of the comboboxes on the subform, the entire record
in the subform immediately has all of it's information in every field
changed to #Deleted.  A search of the MSKB under #Deleted found
information that suggested this happens when an Access FE is using a SQL
BE, but no discussion of an Access FE using an Access BE.  We have been
able to trap an error which indicates that we are trying to do an
rst.update without first doing an rst.edit, but since the forms are
bound to the tables this doesn't make sense.  Also, the code behind the
subform comboboxes doesn't lead to any other code which edits and
updates a recordset.

Any suggestions on what the next steps could be would be greatly
appreciated! 

Thanks, 
Dan Waters 
Quality Process Solutions 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://databaseadvisors.com/pipermail/accessd/attachments/20030307/6125c303/attachment-0001.html>


More information about the AccessD mailing list