Stan, It is possibly because your workspace is trying to execute an operation, such as labelling, on a layer that has had its name changed since the workspace was created. When it tries to label the layer called 'filename' it can't find it and so reports an error.
Have a look at the workspace with a text editor and see if you can find the offending line. HTH Richard -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Stan Johnston Sent: 05 February 2002 00:22 To: MapInfo-L (E-mail) Subject: MI-L "filename.ID not found" error...? I have had in the past and currently a workspace which has tables in map windows where a layer(s) will have the error: 'filename'.ID not found, and the window indicating this error keeps popping up. This seems to be associated with certain tables only. Is it a memory leak issue? I had no problems until certain tables were opened. I don't think it's a memory leak as I had 1800 base map layers working fine without the layers, which caused the error. The error still occurs with only 100 base map layers and the tables, which cause the error message. Stan Johnston B.Sc. Geologist _______________________________________________________________________ List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MapInfo-L" in the message body. _______________________________________________________________________ List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MapInfo-L" in the message body.
