I just wanted to give everyone a heads-up on what is coming up with version
1.05 so that you can plan ahead for the changes.

Due to the needs of the ODBC driver and .NET data provider, along with the
need of some VCL customers to use more than one configuration file in the
same application, the local sessions in 1.05 will allow for specifying many
of the options that are presently part of the engine configuration.
Specifically, the configuration path, configuration file name, file
extension customizations, large file support, encryption password, and
signature options will be customizable from the session level for local
sessions.  The temporary tables path will stay at the engine level.

The end result of this will be that the EDB Manager will be able to access
different configuration files for different sessions at the same time, and
that the ODBC driver and .NET data provider will allow for the above options
to be set via their connection strings, which are equivalent to session
settings.  For the EDB Server, the above options will stay at the engine
level in terms of how they are configured.

In addition, many of the options that currently require a re-compilation of
the EDB Manager or EDB Server will be exposed as configurable in these
applications.  That should make things a little easier on everyone.

Any questions, comments, etc. are welcome in this thread.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>The end result of this will be that the EDB Manager will be able to access
>different configuration files for different sessions at the same time, and
>that the ODBC driver and .NET data provider will allow for the above options
>to be set via their connection strings, which are equivalent to session
>settings. For the EDB Server, the above options will stay at the engine
>level in terms of how they are configured.

Being a bloody nuisance does work - yippee

>In addition, many of the options that currently require a re-compilation of
>the EDB Manager or EDB Server will be exposed as configurable in these
>applications. That should make things a little easier on everyone.
>
>Any questions, comments, etc. are welcome in this thread.

Thank you very much.

Roy Lambert

Excellent, thank you.

Chris Holland


Tim Young [Elevate Software] wrote:
> I just wanted to give everyone a heads-up on what is coming up with version
> 1.05 so that you can plan ahead for the changes.
>
> Due to the needs of the ODBC driver and .NET data provider, along with the
> need of some VCL customers to use more than one configuration file in the
> same application, the local sessions in 1.05 will allow for specifying many
> of the options that are presently part of the engine configuration.
> Specifically, the configuration path, configuration file name, file
> extension customizations, large file support, encryption password, and
> signature options will be customizable from the session level for local
> sessions.  The temporary tables path will stay at the engine level.
>
> The end result of this will be that the EDB Manager will be able to access
> different configuration files for different sessions at the same time, and
> that the ODBC driver and .NET data provider will allow for the above options
> to be set via their connection strings, which are equivalent to session
> settings.  For the EDB Server, the above options will stay at the engine
> level in terms of how they are configured.
>
> In addition, many of the options that currently require a re-compilation of
> the EDB Manager or EDB Server will be exposed as configurable in these
> applications.  That should make things a little easier on everyone.
>
> Any questions, comments, etc. are welcome in this thread.
>

Tim


Question I forgot to ask is "how far ahead should I plan?" or "when is 1.05 due?"

Roy Lambert

Roy,

<< Question I forgot to ask is "how far ahead should I plan?" or "when is
1.05 due?" >>

Hopefully it will be ready within the next few weeks.

--
Tim Young
Elevate Software
www.elevatesoft.com