Went back to look at this again this morning, but changed from 2.3m_1 to StarOffice 8 update 7.
If you want the actual test jet database I am using you can get it at http://www.microsoft.com/downloads/details.aspx?familyid=133DF946-80A4-4913-B18F-2CBC96BF03EA&displaylang=en To make a long story short it appears that the problem is in the queryAnalyzer - now remember I only do black box testing so that is a guess. Here is why I say that. If I open my Base files and create a query using the designer, but then switch escape processing off. Everything runs as one would expect performance wise. The example again from yesterday that causes the major grief with this database SELECT `Customers`.*, `Orders`.*, `Order Details`.*, `Products`.* FROM `Orders`, `Customers`, `Order Details`, `Products` WHERE ( `Orders`.`CustomerID` = `Customers`.`CustomerID` AND `Order Details`.`OrderID` = `Orders`.`OrderID` AND `Order Details`.`ProductID` = `Products`.`ProductID` ) If I run this with escape processing turned off the result set is available on screen in less then 2 seconds. If I turn escape processing back on then even attempting to save the query sends the CPU to 100% and it stays there. ( I can't tell you for how long, cause I don't wait more then a minute before I terminate the process. ) Also, if I save the query with escape processing turned off, but then attempt to add that query into a new query - at the time I try to add it the CPU again pegs. I assume again the query analyzer is coming into play then. I haven't found an Issue dealing with this so I suppose I will go ahead and open one. Jens: I would say then that if you want to use Base to generate some queries for use in Access, you can. You can use the query designer as yo like, just remember to actually turn the designer and escape processing ( by selecting the botton 'Run SQL Direct' ) off before you save or test the query. Drew
