No, it's because the query I'm using is broken - it does a full table scan of one of the fields because that field is currently representing a bitmask (bad old legacy code). The size isn't an issue at all, nor will AJAX do anything. I just need to retro-fit the DB changes we've made in our dev servers onto the live server (which leads to another change which leads to another change and so on). cheers, Chris Maunder CodeProject.com : C++ MVP

...it's big but isn't it just as slow? I get out to malaysia fairly often and the thing that would most affect my journey is it being a heck of a lot shorter! Still mourning the loss of concorde, a plane that STILL hasn't been equalled after decades of 'development', and now just remembered for a crash. Tim Stubbs

I think you might be able to use "port-forwarding." That is to say - create a rule on your router to direct any requests to port 80 on your external IP to your web server. I think it depends on what kind of router you have, and it would make your NAT network less secure. It might be better to go to a NoNAT configuration on the gateway, and have a Local NAT Zone and a DMZ for the webserver. Sorry I can't be more specific on the port forwarding thing - but hopefully it might help you a little. :) Best Wishes Steven let the stormy clouds chase everyone from the place