> I thought that Classic wasn't available for Windows yet.

It's been available since the release of v1.5 and has been running like
a tank for us (30 client deployments).

My only concern about using Classic is that Windows does not do a great
job of managing that many (300-400) processes (each connection would
spawn a new engine instance/OS process).

At the same time, the SuperServer would likely choke when a single
process executes a long running query.

It would seem that you are caught in between two different options.
Most user installs don't involve that many databases on a single server.
So, you will need to check your mileage as you go. Fortunately, the
process from Classic to Superserver is very easy.

I would recommend, however, that you consider running the database under
Linux, which has a much better task/process scheduler and a small OS
overhead.


Sean