Forum Discussion
Access freezes when I copy a record
- Dec 03, 2022I also did that and saw the problem remained
How is the table sorted? What Indexes are on it? I am assuming that it would have a Primary Key, but please confirm that, as well.?
Also, please confirm whether this is a local table in the same accdb, a linked table in a second accdb, or a linked table in a different database, such as SQL Server.
Can you also please provide answers to the questions I asked?
- rick541035Jun 26, 2024Copper Contributor
ms 365 access not responding after doing cut and paste in local tableGeorge_Hepworth
- George_HepworthJun 29, 2024Silver Contributor
This was appended to a discussion with over 100 responses. I don't think I want to read back over the whole thread to see if this is a response to a specific previous comment, or just tagged on to it.
Perhaps, though, if you read the thread and try some of the suggestions offered, you'll find something that resolves your problem.
Personally, I do not recommend copy/paste into local tables as a production method in any event because of the complications involved. It is probably more effective to import data from the source using automation.
- Jeff_BergerMar 14, 2023Copper Contributor
George_Hepworth I am having this same issue over the last few weeks. When I need to update a record (in this case "cut" it to create a different, updated new entry) Access crashes when I "cut" the entry (an entire record). This is a member database with just under 10,000 entries. I have to do CTL-ALT-DEL and stop the program, which has freezed. When I restart it, I can paste the entry as a new entry in the database. Although I've used Access for 20 years, I'm a journalist and have no idea what some of the things you've been saying mean. I DID do "compact & repair" but that did nothing. This is a high end Win11 system. Obviously the most recent update to Access royally screwed something up. If I knew how to restore Access to how it was before the most recent "update" I would. This is very annoying.
- George_HepworthMar 14, 2023Silver ContributorSince you addressed me directly, I'll add a note that a temporary work-around is, as has been suggested a few times in the thread with varying degrees of detail, to Run the application "As Administrator".
- Jeff_BergerMar 15, 2023Copper ContributorThanks George, I'm doing that now and it works but I'm certain we all agree this should have been part of Microsoft's test routine and never should have been in released software. Thx again. Appreciate the help of everyone here.
- bawielandMar 14, 2023Copper Contributor
Jeff_Berger Have you tried opening and running the program *AS ADMINISTRATOR* rather than running it regularly? This magically fixed the problem for me. Rather than starting it as you usually do, right click on the icon and choose "Run as administrator" - It may be hid under the "More" tab. That's all there was to it.
I'm a journalist, too - so if *I* can do it, anyone can 😉
- Jeff_BergerMar 15, 2023Copper Contributor
bawieland THANKS! Much appreciated. -- Jeff
- Art_MeniusNov 18, 2022Brass Contributorjust did
thanks for your help- George_HepworthNov 18, 2022Silver ContributorIt may be a a couple of days, but I sent an alert to MS Access team.
Also, thanks for the details.- Art_MeniusNov 22, 2022Brass ContributorHave you heard anything back from Access team? I have still heard nothing and have been unable to get through to them otherwise. Last post asked for $499 to submit a new ticket.