Thanks Peter & Lars Yes, I'd put some code to close the message window in the wrong place. I moved it to the end of the proc but accidentally put it outside the End Proc. Good catch.
However: 1) wouldn't you think the compiler should notice this error, instead of waiting till link? 2) It was only in one proc but generated 3 spurious error messages. 3) I'd noticed that the compiler also missed my reading from a non-existing cursor (that type of error only pops up when you reach the offending code. As I said, I'm used to these "knock on effect" errors but they're sometimes hard to track if you haven't already been there before. Many thanks Terry -----Original Message----- From: Peter Horsbøll Møller [mailto:[EMAIL PROTECTED] Sent: 11 January 2006 13:45 To: Terry McDonnell Subject: RE: [MI-L] Duplicate Sub or Function MAIN Terry, Make sure that you don't have any code outside any procedure or function. This was the problem the last time, I had this error _______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l
