Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 2 of 2 total |
.lck and memory tables |
Wed, Feb 28 2007 1:58 PM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
I've just realised from your other post that the .lck file must get cleared up a bit. I assume its just memory tables that are affected because the .lck file is also in memory and hence deleted when the app closes? Roy Lambert |
Fri, Mar 2 2007 7:14 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< I assume its just memory tables that are affected because the .lck file is also in memory and hence deleted when the app closes? >> Yes, the issue is more that the in-memory lock files cannot be deleted without exiting the process, unlike the disk-based .lck files. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |