This could be caused by a Form and a SubForm with similar RecordSources.
No the main form is linked to tbl_Membership the subform is linked to tbl_Documents. The tbl_Documents does have a foreign Key to tbl_membership.
Is there any VBA code that might change the same record (in the source table, not the form's recordset) that you are editing in the form?
Try using a QUERY of those table as a Recordsource instead of the tables directly.
John, No there is no VBA in this DB at all yet.
RuralGuy, I use tables as the data needs to be editable.
If you want to provide db for analysis, follow instructions at bottom of my post.
Data can be edited via a simple SELECT query. However, I have doubt query as RecordSource will resolve the issue.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Queries are editable unless you do something weird.
http://allenbrowne.com/ser-61.html
RuralGuy, I'll try that today. Thanks
Ok, made the record source of the main form and the subform queries based on the tables same result. That did not help whatsoever any other ideas? I am at a loss. I am going to try something will let you know in a bit.
As June suggested, post a copy of the database with data to show the issue--remove anything confidential/private.
I'm afraid we're down to you zipping up your db and attaching it to a post. We're just shooting in the blind here.
Okay I narrowed it down. the Tables are in SQL Server I was in the process of copying the tables to the local DB so I could post it and before posting I tested with the forms linked to the local tables it worked just as intended. So the issue has to do with the tables being linked from SQL Server. Posting the DB won't help because it works fine with the tables local.
Do your Tables in SQL Server all have Primary Keys, or at least Unique Indexes, defined for them? Is the PK part of the RecordSource of the Form? These things not being true can cause many problems, including the inability to enter data. The fact that moving the Tables to the Front End resolves the problem tends to support this as being the root of the problem.
BTW, Queries are editable, it’s only multi-table Queries that are frequently non-editable.
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007
I thought they did but I double checked and no they do not. I put the Index on when linking but the source doesn't have the index. I'll fix that and retest thanks.