The normal WebField has been with us for several months by now, but we are still learning.

The "normal" WebField is built directly on top of a Memo field. This is very effective, but it has its limitations.

A "normal" WebPage is referenced to its file location, but since WebField is directly on top of a Memo, there is no file reference. This causes problems with relativity i.e. linking libraries etc. that is stored in a files structure local to the Application.

Another problem is that this is a security breach, as loading scrip files into a webpage that is not local to the server is a big no no!

Since we don't want to get rid of our "speedy" normal webfield, but still want one that can do "everything", we have also implemented an Advanced Webfield.

The Advanced Webfield actually write the content of the supporting Memo to a temporary file in the App catalogue and then loads the file into the WebField object. This way we both take care of security and relativity...i.e. we can reference libraries, images, style sheets etc. relative to the webpage (travels well too...).

With Advanced WebField you can implement any Web Enables functionality in a DFW form.

Applets, Widgets, JQuery, Java....

Again...use your imagination.