Hi! I have encountered the same problem:
maxdb seemingly considers some indizes as to be non - existing and produces Table-Scans... after redesigning t he indizes I was able to eliminate the annoying table scans. I combined one column of the primary key with the index-kandidate-attribut and - DISCO. No Table Scans any more.. Hope that helps... Best Regards, Mit freundlichem Gru�, Ralf Bolduan ENERCON Service GmbH Service-IT Abt.: ADS/SIP mailto:[EMAIL PROTECTED] http://www.ENERCON.de __________________
