Offline XMl Forms

I've done it with Macromedia Shockwave. I just
completed a client side web app using
Shockwave that does XML based forms
validation. This messaging process is
handled using an invitation only closed circuit
encrypted FTP messaging system.
Forms are sent to the client as XML text
messages that the web app determines that
the current message is a form. The user can
fill out the form off line at a later time. This
form has step by step validation built into it. All
forms arecreated using XML so the form
validater has an unlimited number of forms
that it can handle. The user can pause and
resume the form process at any time. If the
user attempts to send the form back after
completing it and the user does not have a live
connection to the internet then the completed
form is sent to the unsent messages memory
container on the users own computer. The
user can send it later as a completed XML /
text formatted message.

I built this messaging system for doctor / client
on-line communications. I could build a
custom version of it for your company if you
have resources to pay for such a version. The
standard version will be going through beta
testing this week and is $199 per doctor. This
means that the doctor puts it up at his/her
website and invites an unlimited number of
clients to communicate back and forth through
the closed encrypted system.

This was created to comply with HIPPA.

One of the cornerstones of XForms (http://www.w3.org/MarkUp/Forms/) is the ability to handle just this situation. Users can fill out the form (with more capabilities than a typical HTML form, by the way) an submit it, saving it locally as an XML file. When they're back in the office, you can simply collect the data, or you can have them submit it to the server.

One of the cornerstones of XForms (http://www.w3.org/MarkUp/Forms/) is the ability to handle just this situation. Users can fill out the form (with more capabilities than a typical HTML form, by the way) an submit it, saving it locally as an XML file. When they're back in the office, you can simply collect the data, or you can have them submit it to the server.

One of the cornerstones of XForms (http://www.w3.org/MarkUp/Forms/) is the ability to handle just this situation. Users can fill out the form (with more capabilities than a typical HTML form, by the way) an submit it, saving it locally as an XML file. When they're back in the office, you can simply collect the data, or you can have them submit it to the server.

If you already have an online version, why reinvent the wheel? Set up a local running web server on each client to run a local copy of the app, saving the xml to the HD. Then, either create a shortcut on their desktop to the save dir so they can transfer the xml when they get back to the office, create a local running script page to tranfer the xml for them. The latter can also be put online behind a secure login for in-the-field access.

If you already have an online version, why reinvent the wheel? Set up a local running web server on each client to run a local copy of the app, saving the xml to the HD. W2K Pro comes with IIS 5, and Win 98 runs PWS. In the unlikely event of a Linux desktop Apache can run locally as well. Then, either create a shortcut on their desktop to the save dir so they can transfer the xml when they get back to the office, create a local running script page to tranfer the xml for them. The latter can also be put online behind a secure login for in-the-field access.

Why not treat your xml pages the same as you can html? Save the page (form) and upload or transfer when back in the office. There must be something more to the form if you cannot use a simple store and forward method as laid out above. At any rate Ihope this helps however basic it might be.