98.7% Of all customers recommend us, we're so confident about our results we publish all reviews and stats
View Live Stats View Reviews
Forum home » Delegate support and help forum » Microsoft Access Training and help » Changes in datasheet view affecting other records | Access forum
Changes in datasheet view affecting other records | Access forum
Resolved · Medium Priority · Version 2007
Mon 16 Jul 2012, 13:42Delegate Paul said...
Paul has attended:
Excel Advanced course
Access Intermediate course
Access Advanced course
Changes in datasheet view affecting other records
I have two fields in a database which, when amended for a single record in datasheet view, incorrectly amend all the entries in that datasheet. The other fields do not behave in this way; and the two affected fields also update correctly without affecting other records when amended in 'form' view'. Any ideas please why this problem might be occurring and how it can be resolved?
Mon 16 Jul 2012, 14:39Trainer Anthony said...
RE: Changes in datasheet view affecting other records
Hi Paul, thanks for your query. There are a number of things that could be causing this and the quickest solution may be to rebuild the relevant tables. If one change in one field is affecting other fields, the original may be involved into calculated fields in queries. However, if these changes don't occur when you switch to form view I would be highly suspicious and immediately start backing up the database and rebuilding. Also try the database on different machines to see if the problem is machine-specific. Sorry to give you so little, but without a close examination of the database it's difficult to advise.
Anthony
Mon 16 Jul 2012, 14:58Delegate Paul said...
RE: Changes in datasheet view affecting other records
Hi Anthony,
Thanks for the quick rersponse. Neither of the fields affected is a calculated field, and the impact is to change the fiield on all records on the datasheet (apart from these two fields the other fields are unaffected). Could the database be corrupt? I'd be very surprised, as it's a farily simple one. Only one table was imported at the build stage (and that table doesn't contain the affected fields); the other half a dozen or so were all condstructed from scratch. In all other respects the DB works fine.
Mon 16 Jul 2012, 15:22Trainer Anthony said...
RE: Changes in datasheet view affecting other records
Any self-joins? Are you looking at the datasheet view of a recordset (query results)? Export the tables into a fresh db and see if the problem is replicated there.
Anthony
Mon 16 Jul 2012, 15:45Delegate Paul said...
RE: Changes in datasheet view affecting other records
Hi Anthony,
No self joins. I am indeed looking at query result record sets. The problem replicates no matter what query is run. However, if I change an entry in the underlying two tables from which the fields are taken, the other records in the table are not affected. Re the fresh db, shouod I export all tables and the data entry form, and then enter some mock records?
Mon 16 Jul 2012, 15:50Trainer Anthony said...
RE: Changes in datasheet view affecting other records
Yes, take everything across - reconstructing may flag up the error. However, you should examine the queries and the table relationships. The recordset you are amending will update the underlying tables which may themselves alter the fields. It's got to be some sort of structural problem.
Anthony
Mon 6 Aug 2012, 12:33Delegate Paul said...
RE: Changes in datasheet view affecting other records
Hi Anthony,
A long time since we had contact on this one. I have done a rebuild, inlcuding inmporting tables and queries one by one, but the problem just replicates. I've also had a close look at both relationships, and properties associated with each of the tables and fie'ds. I can't see anything odd about the two fields which are causing the problem when compared to the other fields which update normally. The really is a puzzle!
Mon 23 Jul 2012: Automatically marked as resolved.
Training information:
See also:
|
Welcome. Please choose your application (eg. Excel) and then post your question. Our Microsoft Qualified trainers will then respond within 24 hours (working days). Frequently Asked Questions
Any suggestions, questions or comments? Please post in the Improve the forum thread. |
Access tip:Compact database automoaticallyTo ensure optimal performance, you should compact and repair your |
