> > Forget the MS scripting engines - they are too much trouble for
> what they
> > are worth!  Firstly, there is no proper debugger, and the languages
> Whats MS Script Debugger then?  I've seen references to it on several
> web-sites I've been looking at.

I won't exactly call the script debugger a proper debugger.  I installed it
once, but decided it was not worth it, so now it is uninstalled!  A debugger
is especially important if you are expecting your clients to write the

> > (vbscript / javascript) are rather limited.  Furthermore, you
> will need to
> > make everything COM before you can export to the scripting
> languages.  Ouch!
> Whilst they may be limited, I don't really need MUCH out of the
> scripts.  Plus you can also get perl, and I think tcl for ActiveScript
> now.

If you must use scripts, I would go for the dreammaker tool, as it gives you
more than just scripts.  It would even let your clients design their own
user interfaces!  However, it too lacks a proper debugger.

One thought.  If the scripts are only used for reporting, try using Crystal
reports.  It can do most of what you can achieve using the basic scripts.

Dennis Chuah, BE (Hons) [mailto:[EMAIL PROTECTED]]
Manager, Product Development
Contec Data Systems Ltd. []
tel: +64-3-3580060 ext-775 fax: +64-3-3588045

    New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]

Reply via email to