IANAM, but I'll take a whack at these.

>1. Object positioning.
>A. I use Absolute Positioning on my forms as I have 100 to 150 objects to present. The web forms I create emulate paper forms that are in use. I have to have control down to the pixel level because of this, otherwise everything will not fit.

The current version uses "Flow" positioning, that is behind the scenes Voodoo places its controls in table elements. While not as precise as absolute positioning, it is quite powerful. It allows you to create say, a Name webform and then subclass it as a Customer webform, adding Customer specific controls that position or flow, after the common Name controls.

>2. What language can be used for validations? VB Script, Java Script, and VFP?

Depends where you're doing the validation. If it's on the server you can use anything you want; if it's on the client, you're limited to whatever it supports - most likely JScript. Voodoo will automatically write the client code to validate the presence of required data.

>3. Can complex forms be created? That is forms to replace those used in complex desktop applications.

Well, we haven't created a Voodoo grid control, if that's what you're looking for. The controls that are implemented in the base package are here: http://www.eps-software.com/voodoo/standard.ewb. The extended package will offer: http://www.eps-software.com/voodoo/extended.ewb.

>4. Support for ADO/SQL Server?

Yes, Voodoo controls can be bound to XML data as well as cursor and ADO based data.

>5. Use of HTML/DHTML?
Not sure what you're asking here. You can stream in your own HTML using the Response.Write method so you certainly have the capability to add your own HTML to the Voodoo page.

Simon
EPS Software

"Any sufficiently advanced technology is indistinguishable from Voodoo"