Thanks for the help guys.
All I have done so far is the local highscore table and plan on having a 'synchronise' button. This will upload any of your scores to website via an encrypted query string on the end of URL, i.e.
http://www.abc.com/abc.php?q=XXXXXYYYYYZZZZZZ
This will then merge your scores with central database (file on disk), and then output new top 50 to the web browser which using urlmon dll will download to a temp file for dbpro to parse and update local high scores. This is similar to how Banshee Studios Asteroids game does it (except that game uses FTP, which is a bit silly).
It may not be a problem as I invisage the operation to be fairly instant like David T says, but there IS a possibility that two people may try and upload their scores at the same time which 'may' cause a problem.
Best thing I can do for now is write a lock file as operation is started encoded with current date and time, do all the synchronisation and then delete the file.
If someone else tries to upload scores and lock file exists AND date and time it was written is less than, say, 1 minute ago, then write out a 'busy - try again later' message. The idea in using date and time is to stop problem where PHP proggy crashes or never completes and lock file stays, stopping any future uploads.
I hope to get all this working today as game deadline is Thursday.
Boo!