Terry,

>I think I figured out what I need to to - I just need to isolate those parts of WC (like POST receive and script return). I don't even know if WC offers a "cFormVars" like varialble for post data or a INT/INI file.

WC provides you a set of objects that mimic the ASP objects: Server, Request, Response, and so forth. You can get to Form vars through Request.Form("name") and URL params through Request.QueryString(3) or Request.QueryString("MyParam") syntax.

>I didn't want to become an expert on WC just yet - my clients know all that stuff (antyway). I just wanted to focus on the so-called "sequencing" engine and build a simple test platform. I have the VFP XOM COM working. It renders all the standards board's test cases - so I am anxious to see how it handles it's other jobs! it was going great with my little mindless CGI/foxISAPI COMS. I had hoped to just work the behaviors of the standard. But a little side trip to WC won't hurt - I'll just have to refill [again] on the SCORM specs later.

Since the final project will be in WC, you might as well work with it now at the prototyping stage, so you'll know what does and doesn't work with your set of circumstances.