Bill, When doing any selection based on an "object", I always adopt that MB solution.
It is one of the cases where the run menu command does not work. The reason seems simple enough: selection-by-polygon is part of the M_TOOL_ family of definitions that requires some mouse input in order to be executed; that cannot be simulated in MB prior to the run menu command. But I suspect that in this precise case the select-by-polygon tool does just what the selection by a single object would do. Bill's question was my before-bed reading and I woke up this morning at 5 having figured out the answer. I was beaten by Uffe who had his 7 hours lead time on me. Unfair eh!, but it is the beauty of the web, isn't it. Jacques -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Uffe Kousgaard Sent: 13 juin 2006 23:36 To: [email protected] Subject: Re: [MI-L] Performance of Large Tables and Spatial Selections Hi Bill, MapInfo is probably applying the Colorado restriction after having joined the 2 tables, which makes it very slow. So start by: Select * from states where name = "Colorado" and store the result in a variable ColoradoObj. Next do: select * from streets where obj within ColoradoObj. Kind regards Uffe Kousgaard www.routeware.dk ----- Original Message ----- From: "Bill Thoen" <[EMAIL PROTECTED]> To: "MapInfo List" <[email protected]> Sent: Wednesday, June 14, 2006 12:03 AM Subject: [MI-L] Performance of Large Tables and Spatial Selections > I've got a large table of streets (the *.map file is a little over 1 GB) > and when I display it over a table of state polygons and select all > streets within a polygon by using a click with the Boundary Select tool, > it does this in a few seconds. But when I try to do this with MapBasic > via a selection like "Select streets.street_name from streets, states > where streets.obj within states.obj and states.name = "Colorado" into > MyStreets noselect" it's taking EONS to do this. Anyone know how I can > get mapbasic to select streets within boundaries, and do it before I > crumble into dust? > _______________________________________________ > MapInfo-L mailing list > [email protected] > http://www.directionsmag.com/mailman/listinfo/mapinfo-l > _______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l _______________________________________________ MapInfo-L mailing list [email protected] http://www.directionsmag.com/mailman/listinfo/mapinfo-l
