> > Classic is the choice if your connection count is likely to

escalate

> > to more than ~300 or so. You just need to give it plenty of
> > RAM. The 2 Gb limitation is irrelevant for Classic, of course.
>
> Also, if the server has multiple processors, use Classic as it will

be

> able to use them all. Compared to Superserver which can only run
> effectively on one processor.

We have a similar situation going now for some time. This is really a
Client Server Application concept. Citrix makes it kind of "thin" for
the clients because the application runs in a chunk of memory at the
server and not at the client.

We have a server with the Firebird 1.5.2 database and several 6+
Citrix servers hitting it. We use a heavy Win32 client (written in
Delphi, of course) that runs on the regular Citrix servers and
provides the users with an application that hits the database hosted
in the Server Citrix machine. The database server is a 4 processor
machine, using hyperthreading to look like 8 processors, and with some
3.5 Gig of available RAM.

We started with Firebird running as SuperServer but quickly changed to
Classic for the reasons mentioned by Helen, among others.

We have some 8-900 theoretical users with less than 300 simultaneous
and have been able to handle the load so far.

Another good thing about this set up is you can scale OK (add more
servers) if you need to.

Hope this helps.

-Eduardo