I am having problems deploying the EDB Server. When I run the client I
get a 600 error because I guess the catalog has an incorrect path to
the data. I want to deploy the database to the user so they don't have
to run any scripts to create the database. How can I correct the
catalog data path from the client software after connection?

Michael,

<< I am having problems deploying the EDB Server. When I run the client I
get a 600 error because I guess the catalog has an incorrect path to the
data. I want to deploy the database to the user so they don't have to run
any scripts to create the database. How can I correct the catalog data path
from the client software after connection? >>

The database catalog does not contain any paths.  The configuration file
contains the path to the database, and you can modify by using the technique
here:

http://www.elevatesoft.com/edb_faqt_2.htm

Are you shipping the edbconfig.edbcfg configuration file with your
application ?  We usually recommend that you do *not* do so and instead
create the necessary users, roles, databases, etc. at application or server
startup.  You can see how this is done in the CDCollector example
application that ships with EDB in the \examples subdirectory under the main
EDB installation directory.

--
Tim Young
Elevate Software
www.elevatesoft.com

On Wed, 30 Jul 2008 17:54:46 -0400, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote:

>Michael,
>
><< I am having problems deploying the EDB Server. When I run the client I
>get a 600 error because I guess the catalog has an incorrect path to the
>data. I want to deploy the database to the user so they don't have to run
>any scripts to create the database. How can I correct the catalog data path
>from the client software after connection? >>
>
>The database catalog does not contain any paths.  The configuration file
>contains the path to the database, and you can modify by using the technique
>here:
>
>http://www.elevatesoft.com/edb_faqt_2.htm
>
>Are you shipping the edbconfig.edbcfg configuration file with your
>application ?  We usually recommend that you do *not* do so and instead
>create the necessary users, roles, databases, etc. at application or server
>startup.  You can see how this is done in the CDCollector example
>application that ships with EDB in the \examples subdirectory under the main
>EDB installation directory.

But in order to do that from the client you need to know the server's
data path. From the client you have no idea what the server's data
path is.

Michael,

<< But in order to do that from the client you need to know the server's
data path. From the client you have no idea what the server's data path is.
>>

You don't do it from the client, you do it from the server.  That is why we
provide the source code to the ElevateDB Server - it allows you to customize
it so that installation in the field is tailored to your needs.

--
Tim Young
Elevate Software
www.elevatesoft.com

On Wed, 30 Jul 2008 20:35:33 -0400, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote:

>Michael,
>
><< But in order to do that from the client you need to know the server's
>data path. From the client you have no idea what the server's data path is.
> >>
>
>You don't do it from the client, you do it from the server.  That is why we
>provide the source code to the ElevateDB Server - it allows you to customize
>it so that installation in the field is tailored to your needs.

You could do it from the client if the server could message the data
path to the client somehow. That way you wouldn't have to code a
server for every app.

Michael,

<< You could do it from the client if the server could message the data path
to the client somehow. That way you wouldn't have to code a server for every
app. >>

You still have to set the configuration file path and other items before the
server can be started for the first time.  And how would the server know
which data path to send to the client ?  You're basically talking about
having the server expose the entire local directory structure to the client,
and I'm not sure if that's a good idea for security reasons.

--
Tim Young
Elevate Software
www.elevatesoft.com

On Wed, 30 Jul 2008 21:31:20 -0400, "Tim Young [Elevate Software]"
<timyoung@elevatesoft.com> wrote:

>Michael,
>
><< You could do it from the client if the server could message the data path
>to the client somehow. That way you wouldn't have to code a server for every
>app. >>
>
>You still have to set the configuration file path and other items before the
>server can be started for the first time.  And how would the server know
>which data path to send to the client ?  You're basically talking about
>having the server expose the entire local directory structure to the client,
>and I'm not sure if that's a good idea for security reasons.

I set the config file path with my server installer by modifying
edbsrvr.ini. I'm just saying it would be convenient to message only
the config file path to the client.

Michael,

<< I set the config file path with my server installer by modifying
edbsrvr.ini. I'm just saying it would be convenient to message only the
config file path to the client. >>

This is something that will be put into place when the EDB messaging layer
is done.  At that time I intend to split the UI away from the EDB Server
itself so that you can remotely hook into the UI, and of course one of
things that you'll also be able to do is to modify the configuration
remotely.  It will also allow you to write a monitoring application that can
detect if an EDB Server has gone down for some reason.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim:

<<<< I set the config file path with my server installer by modifying
edbsrvr.ini. I'm just saying it would be convenient to message only the
config file path to the client. >>

This is something that will be put into place when the EDB messaging layer
is done.  At that time I intend to split the UI away from the EDB Server
itself so that you can remotely hook into the UI, and of course one of
things that you'll also be able to do is to modify the configuration
remotely.  It will also allow you to write a monitoring application that can
detect if an EDB Server has gone down for some reason.>>


Any progress on this?  It looks like it would be very useful.  Any eta for it?

Regards,

Dale

Dale,

<< Any progress on this?  It looks like it would be very useful.  Any eta
for it? >>

Nah, I'm still trying to get 2.03 out and this is scheduled for 2.04.  These
last few months haven't lent themselves to getting any development done due
to the sheer number of new customers and support volume.  We've effectively
had hundreds upon hundreds of customers moving over to ElevateDB and needing
heavy support while they converted from DBISAM, etc..  Things are starting
to quiet down a bit, so I'm hoping that I can get 2.03 finished soon.

--
Tim Young
Elevate Software
www.elevatesoft.com