Thank you, Christof.

I did a more in depth review of JavaScript (ECMA) and was pleasantly surprized to learn that JS. It seems a powerful script engine.

The project requires browsers to run JavaScript. One item the project depended on was an applet, which meant the Apache Server and a JSP engine. That applet inherited a a struture (a container) and some methods from JSP and .class files. Another item in the "sample" runtime was Apache's DOM (getattribute() and selectNodes()) for parsing an XML [hierarchial] manifest.

The only requirement to implement the content is that the browser interpret JavaScript. The sample runtime provided by the "standards" group uses the free Apache and Jakarta. The demo runtime files are js,jsp and java (class).

I was able to convert the intial part of the project to MSDOM2 and have parsed the "manifest" to DB.

My client does not want Apache or JSP "behind" their IIS. After the parse (without the Apache DOM!) I begain to attack that pesky applet. I needed to provide content "actions" with contained methods (like a API.GetValue() and a "API.SetValue()), but without the applet. I also need a structure (container ancestery) that would provide a store or a reference. The object would have propertie names like "CMI.items._count" that the get/set values would work with.

With JavaScript, the objects can be created for both the stores and the methods, and the "content" will be able to interact just like it did in the sample runtime, but without the .java and jsp.

It is a hairy project. Most of the work is managed by the "content" through a generalized ""API" interface. The content includes sequencing and rollup behaviors to "managage" client intereaction - but I have just began to devine that stuff!

But the JavaScript is amazing - I did not know it could do all those things (objects and function objects and array objects!).

SCripting (http://www.ashleyit.com/rs/main.htm).
Thanks for this one!

Do you mean "Apache DOM" or "Apache COM"? "Apache DOM" is an XML parser. DOM in the context of Java Script refers to the document model of the browser, whereas Apache is a web server. COM would imply that Apache somehow is available as a COM server.
I meant DOM and the DOMTreeUtility:). Got that part working through VFP and MSXML2.DOMDocument4.0.

>
>>I don't think I need to reference the COM - only the structure that results from the "instance" of the COM.
>
>I don't think I understand what you mean here. But we're getting somewhere. :)

And you're patience shall be rewarded - thanks!