Hi everybody, Does anybody know how to better use the MI spatial index built on ODBC tables? when uploading a 100'000 point records it took nearly one hour to generate this 17 letters index but when I try to download point with a spatial criteria (i.e. within current_mapper) I actually loose a bit of performance in comparison with the no index option in the make table mappable. I'm working with the 4.5 version of MI with MS ACCESS 97 and ODBC drivers 3.51.102900 if it is a version problem Am I missing something in the set up? (maybe index on the index?) How many records do I need to have to actually profit from the spatial index structure? Thanks for the help Tomaso Bertoli Metropolis - Spatial Decisions Cape Town, South Africa ---------------------------------------------------------------------- To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
