Paul Beach wrote:

>
> But with the Vulcan Architecture it does... instead of shipping three
> different versions of the server, changing a setting in the conf file(s)
> will determine how Vulcan acts - SuperServer with SMP, Process based (Classic) or
> Embedded... now get your marketing head around that :-)
>

And you can choose different settings for different databases - and
mix a multi-user server with local classic on the same database. It's
reasonably cool.


Regards,


Ann