I've got a problem where a feature class lock file is not going away when it should. I discovered the problem when developing an ArcMap add-in using a file geodatabase, but I drilled it down to a simple procedure that recreates the problem. I was hoping that somebody else could test this and offer any ideas. Here's how it goes:
Open a blank map.
Add a shapefile to it, observe the lock file in windows explorer.
Make an edit to the shapefile, save edits, stop editing.
Save the map, keep it open.
Remove the shapefile from the map.
For me and another PC I tested on, the lock file still exists, but it shouldn't.
It seems to be a combination of the editing and saving of the map, do either of these actions by themselves then remove the shapefile from the map and the lock file goes away. Could anybody test this simple procedure and let me know if it does the same thing? Thanks.
I'm running ArcGIS Desktop 10.0, SP 5.
Open a blank map.
Add a shapefile to it, observe the lock file in windows explorer.
Make an edit to the shapefile, save edits, stop editing.
Save the map, keep it open.
Remove the shapefile from the map.
For me and another PC I tested on, the lock file still exists, but it shouldn't.
It seems to be a combination of the editing and saving of the map, do either of these actions by themselves then remove the shapefile from the map and the lock file goes away. Could anybody test this simple procedure and let me know if it does the same thing? Thanks.
I'm running ArcGIS Desktop 10.0, SP 5.