Dear MB developers, If you have any MapBasic applications which use the line 'Run Menu Command M_FILE_SAVE_WORKSPACE', they may fail to work properly under some circumstances (see below) with MapInfo 5.x. Richard Burkmar. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: 09 November 1999 18:03 To: [EMAIL PROTECTED] Subject: Re: MapBasic 5.x Bug This is a bug in MapInfo 5.5 as well. I will file it as a bug. Unfortunately, I don't have a workaround for this. Cindy MapInfo Technical Support * To: TechSupport/MapInfo Corp@MapInfo Corp cc: Subject: MapBasic 5.x Bug > Tech-support, > > When I compile and run the following MapBasic 5.0 program, I get an error > if I have previously run an SQL query and I have the 'save queries in > workspaces' option set (i.e. if the workspace tries to save the query). > Running 'save workspace' directly from the MapInfo menu is OK as is > running the MBX if I have not first run an SQL query or running the MBX > with the 'save queries in workspaces' option not set. > > Include "Menu.def" > Declare Sub Main > > Sub Main > Run Menu Command M_FILE_SAVE_WORKSPACE > End Sub > > This is causing us problems because we have a MapBasic App (originally > written at version 4.x) which intercepts a user's request to save a > workspace from the MapInfo file menu and runs some code to clear up > application-specific tables before saving the workspace with a line like > that shown above. Now a customer has moved to version 5.x of MapInfo, and > cannot save workspaces with queries (which they need to do) unless they > first shut down the application. > > Do you have any workarounds or bug fixes for this problem? > > Richard Burkmar ---------------------------------------------------------------------- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]