Working offline as you describe is fairly complicated.
If the data is add-only, you can create a Web page that
reads the off-line database and inserts to the online
(centralized) database. However, you must somehow guard
against duplicate insertions, and you must provide some
way to correct the data after insertion.
Life gets more complicated if you want to download,
update, and upload. In that scenario, you have to check
somehow whether the data in the central database has
changes, and then implement some sort of conflict
resolution.
I could answer your question more precisely if you
explained more about the application, but I'm fairly sure
it would require a lot of programming in ASP, ASP,NET, or
whatever your server supports.
Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------