Hi,

I have migrated our DB on my PC from DBISAM 3 to EDB (after creating a session and a database of course) use the EDB Manager with no problem
but, when I moved the whole folder that has the DB to another PC with another drive-letter (D: instead of Cthe application could not recognize the
DB or the session.  I know this has to do something with the configuration file and the catalog file.  However, the question is: what are the right steps
to identify (Create/Reconfigure) the session/database in a new pc or a pc that has a DBISAM 3 database?  Our application is a distributed one and
we prefer to embed those steps in our application since we will be migrating from DBISAM 3 to EDB in the next future.

Regards,
Abdulaziz Jasser

Abdulaziz,

<< I have migrated our DB on my PC from DBISAM 3 to EDB (after creating a
session and a database of course) use the EDB Manager with no problem but,
when I moved the whole folder that has the DB to another PC with another
drive-letter (D: instead of Cthe application could not recognize the DB
or the session.  I know this has to do something with the configuration file
and the catalog file.  However, the question is: what are the right steps
to identify (Create/Reconfigure) the session/database in a new pc or a pc
that has a DBISAM 3 database?  Our application is a distributed one and we
prefer to embed those steps in our application since we will be migrating
from DBISAM 3 to EDB in the next future. >>

1) Make sure that the TEDBEngine.ConfigPath property is valid for the new
location of the application.  We usually suggest that you use the path for
the application .EXE, although with XP and Vista it is getting harder to do
so and you usually end up having to use the Common Application Data folder
under Windows instead for your app-specific data.  You can actually get this
very easily with a little "shortcut" property:

Engine.Handle.Environment.CommonDataDirectory

Just append your app-specific path information to the end like this:

Engine.ConfigPath:=Engine.Handle.Environment.CommonDataDirectory+'\My
Application';

2) Then, follow the steps here to reset the path(s) for any defined
database(s):

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

You can use the TEDBSession.Execute method to execute this statements
quickly:

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

--
Tim Young
Elevate Software
www.elevatesoft.com

> Engine.ConfigPath:=Engine.Handle.Environment.CommonDataDirectory+'\My
> Application';

Can I use this function when installing the application on older windows
version
like Win 98/95
Sorin

Sorin,

<< Can I use this function when installing the application on older windows
version like Win 98/95 >>

You'll need to make sure that they're using at least IE 5.0 or higher.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:02E4355E-9C80-453A-81DA-741CA419584B@news.elevatesoft.com...
> Sorin,
>
> << Can I use this function when installing the application on older
> windows version like Win 98/95 >>
>
> You'll need to make sure that they're using at least IE 5.0 or higher.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com

Tim, what can the browser have to do with this?

RoyJ

Royke


As a guess Engine.Handle.Environment.CommonDataDirectory uses an API call with is only present in newer versions of the browser.

Roy Lambert

Roy,

<< Tim, what can the browser have to do with this? >>

In Windows 9x, the version of IE that you used affected which shell
functionality was available since the shell was implemented in the IE DLLs.

--
Tim Young
Elevate Software
www.elevatesoft.com

Sounds like a hassle. Why is this not implemented as a property that can be altered to point to new folder that contains the db? Like firebird or
nexusdb?

Tim,

<< Sounds like a hassle. Why is this not implemented as a property that can
be altered to point to new folder that contains the db? >>

First of all, I don't think that executing one ALTER DATABASE statement is
any more difficult than changing a property.  In fact, the ALTER DATABASE is
very easy to do, especially in the EDB Manager if you use the dialog to do
so.

As for why it isn't a property, the database names are referenced in the
configuration information, so the same database name must always point to
the same database directory, and having them in the configuration
information enforces this requirement.  If the database name/location was a
property, then it would be possible to have multiple client applications
using the same database name with different physical databases, and that is
not a good thing in EDB because it breaks the user security and locking.

--
Tim Young
Elevate Software
www.elevatesoft.com