Thanks to all those who responded to my question. It turned out to be quite a simple problem to solve. I acually tried deleting the TIN files, as directed below, before I posted my questions. Simply freeing up some disk space solved the problem for me. The reponses I received were: >From Martin Roundhill: sounds like a disk capacity problem or files with the read only flag set but I am guessing you have already looked at this. >From John Schlosser: This table was being edited by someone who exited, crashed, or otherwise stopped abruptly. Doing this leave the *.tin and related tmp files made by MapInfo when editing a table. You can normally safely delete the files with extensions *.tda and *.tin. But make a backup first, just to be sure. >From Trey Pattillo: Without anyone logged in look at the folder where some suspect tables are The *.TIN, *.TDA, *.TMA are tempoarary editing files for the index, data, and map files. This is what allows for the undo function and "fast editing". If these files exist without anyone using MI anywhere on the network, then they got there from a computer crash that left the tables in a *still editing* state, something similar happens with other software, I have much experience with Word Perfect doing it, and those apps will start up with messages like *file ???? was not save -- what do you want to do -- open/trash". NOT true with MI. You get the table more or less [less] as as *read-only* so any attemt at editing with fail and give messages. >From Tom Manson: Here's a guess you might try: Get out of MapInfo and on the disk where your table is, get rid of the temporary files for that table (*.TIN, *.TDA, *.T?? (except don't erase *.TAB!) etc.). I think these are the "flags" that tell one copy of MapInfo that another user has edited the table and not yet saved the edits. There may be a key in the *.map header that serves as a lock that will need to be reset, but I don't know for sure (I know two people here who might know that though!) >From Peter Thake: Sometimes Mapinfo does not close properly, leaving an instance of Mapinfo running (although you will see no evidence of this on your desktop). This is particularly common when running a VB/MapBasic/MapInfo application that crashes or locks up. This can cause the message you listed to be given. Try bringing up the Task Manager (ctrl-alt-delete) and end any instances of Mapinfow.exe. Or the problem could simply be that you have a shared table that is being edited on another PC. >From Jonathan Stokes: check to see if there are three extra files with the same 'name' as you table but different extensions. they are from memory called .tma .tin and one other i can't remember. i think they are the equivalent of a record locking file in Access - they prevent another user editing a table that is already being edited. If you've crashed out of an edit in MapInfo they may still be there as MapInfo has not completed the edit and cleaned up after itself >From Sheila Quon: I have encountered this problem too! Really annoying. MI sometimes develops this bug. The way to overcome it is to delete the *.tin file in the relevant subdirectory. That should solve your problems! ************************ Tim Smith Urban Wilds Project Manager Boston Parks 617-635-4505, ext. 6511 617-635-3256, fax ************************ ---------------------------------------------------------------------- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
