$ 0 0 Thanks Chris. The SQL(BEHAVIOR=UNOPTIMIZED) fixed the problem. I will also look into using the newer ODBC drivers.