can't say for sure, but i think the SQL runner can resolve objects and such by defining them invisibly at run-time. however if you're doing stuff through code, then it expects that you are taking control of all aspects, including the creation and destruction of variables. something like: ############## dim thisobj as obj thisobj = selection.obj Select * from propertynotes where thisobj within propertynotes.obj into findparcel
undim thisobj ############## that's just off the top of my head, so some tweaking may be necessary. -----Original Message----- From: Doug Pease [mailto:[EMAIL PROTECTED] Sent: Wednesday, 29 October 2003 9:58 AM To: [EMAIL PROTECTED] Subject: MI-L run command error problem Im stumped with what might have a very simple solution, but I am unable to work it out. Hope someone can help me out here. In an application I run a very simple query : Select * from propertynotes where thisobj within propertynotes.obj into findparcel Thisobj is defined as an Object When the query is run directly as a query it produces results. If I run the query as a command string I get the following error: "Variable or field thisobj not defined" Any assistance greatly appreciated. Doug Pease GIS Officer Livingstone Shire Council PO Box 600 Yeppoon 4703 Qld Australia Ph 07 49399957 Fax 07 49393290
