>>> recollection is that Classic processes do not influence each other so if one
>>> of the ugly reports is run, the other users won't be affected.
>
> Correct
>
>>> I have to stay with FB 32-bit for now until I
>>> can replace the few FreeUDFLib functions used in the database. I may try to
>>> do this before they bring up the new server so I can use FB 64-bit.
>
> I was in the same boat. Managed to find replacements for all the FreeUDFLib functions I was using with Fb 2.1.
>
>>> And with Classic you can't perform
>>> backup/restore programmatically over the network, you have to be local on
>>> the server.
>
> Why do you say that, I do backups and restores over the network all the time with classic
>
> I did find that with Fb 1.5 with classic I needed to put quotes around things that I mustn't with superserver, but with FB 2.1 I no longer need to do that.
>
>>> It looks like Classic can handle multiple CPUs better than Superserver
>
> Yup, that's why its popularity returned, even though the technology is older.
>
>>> and events can't be used if the server is behind a firewall or
>>> secure tunnel. (everyone is on the same side of the firewall in this case)
>
> AFAIK, this is the same whether you're using CS or SS, but I haven't done much more than just play around with events a bit

Up to 2.1, the RemoteAuxPort in the configuration file for defining a
single TCP port for event communication doesn't work CS, thus events
with CS in combination with a firewall might create problems.

In 2.5, the mentioned configuration parameter works across all
architectures.




--
With regards,

Thomas Steinmaurer
Upscene Productions
http://www.upscene.com
http://blog.upscene.com/thomas/

Download LogManager Series, FB TraceManager today!
Continuous Database Monitoring Solutions supporting
Firebird, InterBase, Advantage Database, MS SQL Server
and NexusDB!