Hi Chris, This is a function of MapInfo SQL. I'm not sure why it is tied to 256 characters ... possibly because it is tied to original DOS roots, or it becomes too hard to find syntax errors, given MapInfo's obscure syntax messages. The SQL dialog box is also rather pokey to work in for long SQL's.
The only way around this is programmatically through MapBasic, and to this end, we've developed Data Assistant, the data validation, querying and table updating utility for MapInfo. From our tests, we can write SQL's to 630 characters. This is done through the Query Wizard. I invite you to download our utility Data Assistant (for MapInfo) at www.datadirections.com.au , install it, and select Data Assistant > Query Wizard > New. From there, it is just a matter of stepping through the dialog boxes to create your SQL. This utility will run for 50 sessions prior to a timeout. A detailed PDF manual and comprehensive help file is also part of the installation. If you have any queries, please contact me. Regards, Bill --------------------------------------- William Donaldson GIS Applications Manager Data Directions ABN 36 661 107 925 240 Jersey Street Wembley, WA 6014 Australia phone: 08 9284 1889 fax: 08 9387 1265 mobile: 0401 67 1889 email: [EMAIL PROTECTED] web: www.datadirections.com.au -----Original Message----- From: Chris Prescott [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 27 November 2002 11:13 To: [EMAIL PROTECTED] Subject: MI-L Save Template limitations All of the fields in the 'SQL Select' dialog box have a limit of 256 characters that can be entered into the box. I have a query that has 233 characters in the 'Select Columns' portion and it executes correctly. However when I save the query (Save Template) and reload it, it fails to execute. The reason for this is that MapInfo inserts numerous spaces into the string, causing it to exceed the 256 character limit. For example, my original query was ... RDSEGDAT.Road_name, RDSEGDAT.Rd_segmtno, ProspectFootpaths_2002.Side, RDSEGDAT.from, RDSEGDAT.to,..... But after saving it and reloading the following is displayed... RDSEGDAT . Road_name , RDSEGDAT . Rd_segmtno , ProspectFootpaths_2002 . Side , RDSEGDAT . from , RDSEGDAT . to ,..... MapInfo has inserted a space before every comma and before and after every dot, making this SQL useless. My questions are (particulary to MapInfo) why is there a 256 character limit on these fields and why are the unnecessary spaces added? Is there any fix to this? Thanks, Chris CHRISTOPHER PRESCOTT GIS Specialist TONKIN CONSULTING 5 Cooke Terrace Wayville SA 5034 T +61 8 8273 3100 F +61 8 8273 3110 E [EMAIL PROTECTED] PRIVACY & CONFIDENTIALITY NOTICE This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom it is addressed. This communication may contain material which is legally privileged and any misuse of this e-mail and any file attachments is strictly prohibited. If you have received this e-mail in error, please delete it and any attachments immediately and notify the first sender by e-mail or by telephoning +61 8 8273 3100. You may rely on documents and drawings received by e-mail when confirmed by a signed Tonkin Consulting hardcopy. Whilst we have used appropriate software to alert us to the presence of computer viruses, we cannot guarantee that this e-mail and any files transmitted with it are free from them. --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 4295
