I find myself adding this AND clause to just about any spatial query I use- "Region" may also be "Line", "Pline", etc, however, region is most common way to use it. The table it needs to reference is the one with the objects you are using to select with, not needed for the objects of the target table. In a perfect world, object types are homogenous in a table, but I happen to live just next door and find this helpful.
AND Str(MyTable.obj)="Region" Real world example Select * from Str_grid, Parcels where Str_grid.Obj Within Parcels.Obj AND Str$(Parcels.obj)="region" into Selection William "Woody" Woodruff Zoning Administrator Charter Township of Union, Isabella County, Michigan -84.80947000 43.61095100 2010 S Lincoln Rd, Mt. Pleasant, MI 48858 (989) 772 4600 EXT 41 Visit our web site at http://www.geocities.com/ctuzoning/index.htm -----Original Message----- From: Don Guerra [mailto:[EMAIL PROTECTED] Sent: March 17, 2004 10:27 To: MapINFO (MapINFO) Subject: MI-L SQL Select Error Thanks Spencer, that helped a lot. I was able to determine that 13 out of 893 objects were in fact not polylines and this is what's hanging up the SQL select. Thanks to Mike Cummings also for his suggestion, however I had already packed the table when I first got the error. Donald Guerra Municipal Authority of Westmoreland County P.O. Box 730 Greensburg, Pa 15601 724-834-6500 x182 --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 10970
