I like option B dumping straight to the front end, but I'm not familiar enough with SQL or Access to know how to use cursors. I suppose now is as good of a time as any to learn. This is something that takes place in the DB engine, right? I'd have to find how to implement this somewhere in Access documentation.

Building a temp table on the backend is a bit more convoluted than I was aiming for. I'm not too sure I'd get much more performance out of that, then my current work around. Right now I have the query bringing back all records, and then using PHP code to control what's actually printed out. Doesn't seem too slow now, but I'm worried it's not scalable to large data sets and many concurrent users sessions.

I miss MySQL.

- Chris
32GB MK2 090000664 Smoke
Queue # 2 (who the heck was 1?)