Mark,

I might have the answer. It looks like the problem is with a query that uses the result of MAX() on one field in an ORDER BY clause - it involves a join of two tables. A likely scenario is that I never tested with multiple records in the second table (in MySQL), and that blew it up on the production server.

Noting that the query didn't do quite what I wanted anyway (a long post in itself), I rewrote it to be more general (and no doubt less efficient). I put the production box back to using 4.0.13 long enough to run a test, and I was able to do what I could not do before. The Access database is back in place, at least until I get a chance to re-run the import.

Next, I'll try to assemble a simple example that causes the problem. More later.

Bill

Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254

Email: bil...@anest4.anest.ufl.edu Tel: (352) 846-1285 FAX: (352) 392-7029