Hello Jim,

Tuesday, September 28, 2004, 2:11:38 PM, you wrote:

> Vulcan has abandoned the alias mechanism in favor of a more powerful
> database configuration mechanism. Database configurations can be
> wildcarded with reasonably intelligent filename rewriting as well as
> per-database configuration parameters. Configuration files are designed
> to cascade, so an individual configuration file could cascade to a
> project file cascading to a site file cascading to the distribution
> configuration file.

So, how would a typical TCP/IP connection string would look like?
Right now with aliases, it looks like: <server_name>:<alias_name>

> An API isn't really appropriate, though a GUI tool
> to manage the suckers might be.

As long as the files can be easily changed without a GUI app.

--
Best regards,
Daniel Rail
Senior Software Developer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)