Your example is set for a D drive, which I don't have, so I put it on a
drive I did have...and changed the ConfigPath in the connection string
builder.

However, when running it, it generates an error that it cannot create
D:\Temp\EDBDatabase.EDBCat and so will not run.

How can this be made location generic?

Also, when I try to create a session in EDBManager, I get the #100 EDB
error.

Is this a Unicode database? And it is version 2, correct?

"Chris Holland [Team Elevate]" <mail@chrisholland.me.uk> wrote in message
news:218429EE-A5F1-407D-9828-C7D6B73C283B@news.elevatesoft.com...
>

Hi Alan,

It was just a quick and rough example to demonstrate the
ConnectionString usage. It is a Version 1 database (I don't have version 2)

There are several ways to change the location of the catalog file, you
can store the path in a config file or else extract the path from the
..exe and point to a subdirectory under where the main application is stored.

I belive in EDB that if you change the path to the tables then you have
to change the "Database" in the Catalog file, but I have never used EDB
in a real world application so far.

Chris Holland

Alan Questell wrote:
> Your example is set for a D drive, which I don't have, so I put it on a
> drive I did have...and changed the ConfigPath in the connection string
> builder.
>
> However, when running it, it generates an error that it cannot create
> D:\Temp\EDBDatabase.EDBCat and so will not run.
>
> How can this be made location generic?
>
> Also, when I try to create a session in EDBManager, I get the #100 EDB
> error.
>
> Is this a Unicode database? And it is version 2, correct?
>
> "Chris Holland [Team Elevate]" <mail@chrisholland.me.uk> wrote in message
> news:218429EE-A5F1-407D-9828-C7D6B73C283B@news.elevatesoft.com...
>
>

Hi Alan,

Try this one.

It searches for a file that is known to exist and if it is not found
then pops up a dialog where the user can select the path to the data.
Then it alters the applications data path and also the database path in EDB.

Again a quick and dirty proigram, but should point you in the right
direction.

Chris Holland
[Team Elevate]

Chris Holland [Team Elevate] wrote:
> Hi Alan,
>
> It was just a quick and rough example to demonstrate the
> ConnectionString usage. It is a Version 1 database (I don't have version 2)
>
> There are several ways to change the location of the catalog file, you
> can store the path in a config file or else extract the path from the
> .exe and point to a subdirectory under where the main application is
> stored.
>
> I belive in EDB that if you change the path to the tables then you have
> to change the "Database" in the Catalog file, but I have never used EDB
> in a real world application so far.
>
> Chris Holland
>
> Alan Questell wrote:
>> Your example is set for a D drive, which I don't have, so I put it on
>> a drive I did have...and changed the ConfigPath in the connection
>> string builder.
>>
>> However, when running it, it generates an error that it cannot create
>> D:\Temp\EDBDatabase.EDBCat and so will not run.
>>
>> How can this be made location generic?
>>
>> Also, when I try to create a session in EDBManager, I get the #100 EDB
>> error.
>>
>> Is this a Unicode database? And it is version 2, correct?
>>
>> "Chris Holland [Team Elevate]" <mail@chrisholland.me.uk> wrote in
>> message news:218429EE-A5F1-407D-9828-C7D6B73C283B@news.elevatesoft.com...
>>
>>

Hi Alan,

Try this one.

It searches for a file that is known to exist and if it is not found
then pops up a dialog where the user can select the path to the data.
Then it alters the applications data path and also the database path in EDB.

Again a quick and dirty program, but should point you in the right
direction.

Chris Holland
[Team Elevate]

Chris Holland [Team Elevate] wrote:
> Hi Alan,
>
> It was just a quick and rough example to demonstrate the
> ConnectionString usage. It is a Version 1 database (I don't have version 2)
>
> There are several ways to change the location of the catalog file, you
> can store the path in a config file or else extract the path from the
> .exe and point to a subdirectory under where the main application is
> stored.
>
> I belive in EDB that if you change the path to the tables then you have
> to change the "Database" in the Catalog file, but I have never used EDB
> in a real world application so far.
>
> Chris Holland
>
> Alan Questell wrote:
>> Your example is set for a D drive, which I don't have, so I put it on
>> a drive I did have...and changed the ConfigPath in the connection
>> string builder.
>>
>> However, when running it, it generates an error that it cannot create
>> D:\Temp\EDBDatabase.EDBCat and so will not run.
>>
>> How can this be made location generic?
>>
>> Also, when I try to create a session in EDBManager, I get the #100 EDB
>> error.
>>
>> Is this a Unicode database? And it is version 2, correct?
>>
>> "Chris Holland [Team Elevate]" <mail@chrisholland.me.uk> wrote in
>> message news:218429EE-A5F1-407D-9828-C7D6B73C283B@news.elevatesoft.com...
>>
>>

Alan,

<< However, when running it, it generates an error that it cannot create
D:\Temp\EDBDatabase.EDBCat and so will not run.

How can this be made location generic? >>

You have to use the ALTER DATABASE statement to change the path of the
database to reflect your environment:

http://www.elevatesoft.com/manual?action=mantopic&id=edb2sql&category=10&topic=93

<< Also, when I try to create a session in EDBManager, I get the #100 EDB
error.

Is this a Unicode database? And it is version 2, correct? >>

..NET is 100% Unicode, so you have to use the Unicode EDB Manager and Server
when working with configurations and databases that will be used by the .NET
data provider.

--
Tim Young
Elevate Software
www.elevatesoft.com

Okay...that explains that. I missed that fact somehow...



..NET is 100% Unicode, so you have to use the Unicode EDB Manager and Server
when working with configurations and databases that will be used by the .NET
data provider.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks, I will give it a try...part of my problem is that I didn't not know the .NET provider was all Unicode, which Tim explained below. I
somehow missed this.

I will have to convert the database I'm trying to access.



"Chris Holland [Team Elevate]" <mail@chrisholland.me.uk> wrote:

Hi Alan,

Try this one.

It searches for a file that is known to exist and if it is not found
then pops up a dialog where the user can select the path to the data.
Then it alters the applications data path and also the database path in EDB.

Again a quick and dirty program, but should point you in the right
direction.

Chris Holland
[Team Elevate]

Chris Holland [Team Elevate] wrote:
> Hi Alan,
>
> It was just a quick and rough example to demonstrate the
> ConnectionString usage. It is a Version 1 database (I don't have version 2)
>
> There are several ways to change the location of the catalog file, you
> can store the path in a config file or else extract the path from the
> .exe and point to a subdirectory under where the main application is
> stored.
>
> I belive in EDB that if you change the path to the tables then you have
> to change the "Database" in the Catalog file, but I have never used EDB
> in a real world application so far.
>
> Chris Holland
>
> Alan Questell wrote:
>> Your example is set for a D drive, which I don't have, so I put it on
>> a drive I did have...and changed the ConfigPath in the connection
>> string builder.
>>
>> However, when running it, it generates an error that it cannot create
>> D:\Temp\EDBDatabase.EDBCat and so will not run.
>>
>> How can this be made location generic?
>>
>> Also, when I try to create a session in EDBManager, I get the #100 EDB
>> error.
>>
>> Is this a Unicode database? And it is version 2, correct?
>>
>> "Chris Holland [Team Elevate]" <mail@chrisholland.me.uk> wrote in
>> message news:218429EE-A5F1-407D-9828-C7D6B73C283B@news.elevatesoft.com...
>>
>>