Avoiding Corruption
- Thread starter JamesJoey
- Start date
- Local time
- Yesterday, 20:38
- Joined
- Feb 28, 2001
- Messages
- 30,155
It appears that some folks don't think this "Clear Cache on Close" setting matters.
stackoverflow.com
My question is whether you used the trick of using a "keep open" method - i.e. open a recordset to a dummy table for the purpose of keeping the I/O channel open. This is because Access will share that channel rather than open another one - thus avoiding repetitive network lock arbitration. The thing to understand here is that the I/O channel doesn't correlate to the table pathway because Access SHARES (internally) those pathways when they lead to the same place.
I believe that if you REALLY do a "hard close" then the cache MUST be cleared, based on Windows security rules regarding object re-use. If you did some kind of "soft" shutdown, maybe the I/O channel is still alive.
I defer to my colleague theDBguy regarding the AutoCorrect and NameChanges settings.
Clearing Access Cache
I am developing a system in Access talking to a Sql Server backend. I can connect with two separate accounts A and B so that I can control permissions. In particular I have a view which is accesse...
stackoverflow.com
My question is whether you used the trick of using a "keep open" method - i.e. open a recordset to a dummy table for the purpose of keeping the I/O channel open. This is because Access will share that channel rather than open another one - thus avoiding repetitive network lock arbitration. The thing to understand here is that the I/O channel doesn't correlate to the table pathway because Access SHARES (internally) those pathways when they lead to the same place.
I believe that if you REALLY do a "hard close" then the cache MUST be cleared, based on Windows security rules regarding object re-use. If you did some kind of "soft" shutdown, maybe the I/O channel is still alive.
I defer to my colleague theDBguy regarding the AutoCorrect and NameChanges settings.
isladogs
MVP / VIP
- Local time
- Today, 02:38
- Joined
- Jan 14, 2017
- Messages
- 18,819
There are some experienced developers who do switch off name autocorrect completely as it can be problematic. In fact one well known member of this forum always refers to the feature as name autocorrupt.
However, in my opinion, used with care it can be very useful. I normally use the same settings as @theDBguy but temporarily switch on Perform AutoCorrect when appropriate. I also never bother clearing the cache as I have another method for dealing with issues such as those described in the very interesting Stackoverflow thread.
However, in my opinion, used with care it can be very useful. I normally use the same settings as @theDBguy but temporarily switch on Perform AutoCorrect when appropriate. I also never bother clearing the cache as I have another method for dealing with issues such as those described in the very interesting Stackoverflow thread.
Isaac
Lifelong Learner
- Local time
- Yesterday, 18:38
- Joined
- Mar 14, 2017
- Messages
- 11,106
Miscellaneous other thoughts on avoiding corruption
Error #5 after compact and repairing
Hi, I just found an error on my db and was looking for some advice. I was working on my forms, looking to improve some things, when by mere accident I clicked the compact & repair button. After that, the welcome form started giving me error #5. Looking through, the problem was the Select case...
www.access-programmers.co.uk
- Local time
- Yesterday, 21:38
- Joined
- Feb 19, 2002
- Messages
- 47,054
If you do not completely understand how Name AutoCorrect works, it is too dangerous to leave on. Leave it off. Turn it on when you need it to help you. Make sure ALL updates are propagated and turn it off again. Leaving it on but not allowing it to propagate is a recipe for disaster.
Similar threads
