Hi experts!
I have just started using EDB, coming from DBISAM.
I have created an app which runs fine on the develop pc.
I use an engine component, a session component, a database component and a
number of table and datasource components.
But when I deploy the app to another machine I get error 401 - The table or
view <name> does not exist.

This is an app with a local database.
I have copied the exe, the database folder and the temp folder to the test
machine.

On compiling I left the engine component inactive and the properties for the
config and temp paths were open. I set these properties to valid paths in
the engine's before start event. The engine type is etServer (no server).

The session type is stLocal.

Is there anybody who can give me a hint where to look. I seem to have
followed Tim's manual all the way, but I still get the error.

Kind regards
TorB.

TorB,

just copying the files won't work unless the path to the database folder (e.g.
C:/MyDatabase) is exactly the same on both machines.

You have to use the ALTER DATABASE statement to set the new path.

Heiko

TorB.

> On compiling I left the engine component inactive and the properties for
> the config and temp paths were open. I set these properties to valid
> paths in the engine's before start event.

Probably you just missed to create the database. You have to do this in
order to access your tables.

Uli

Thank you guys.
I'll check if this works on the deploy machine.
A little more complicated than DBISAM...
Kind regards
Tor B.

****

"Ulrich Becker" <johnmuller54@googlemail.com> skrev i melding
news:49D68761.9090306@googlemail.com...
> TorB.
>
>> On compiling I left the engine component inactive and the properties for
>> the config and temp paths were open. I set these properties to valid
>> paths in the engine's before start event.
>
> Probably you just missed to create the database. You have to do this in
> order to access your tables.
>
> Uli

Tor,

<< A little more complicated than DBISAM... >>

Just different, actually.  If you think of the CREATE DATABASE/ALTER
DATABASE as the equivalent of setting the TDBISAMDatabase.Directory property
in DBISAM, you'll see that it is exactly the same process.  The only
difference is that the EDB path specification for a database is persistent
in the configuration instead of simply being a property value.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thank you, Tim!
I can see that now after studying EDB manuals a bit more.
The case I asked about is working now.
My main concern now is how to deploy my apps when I use EDB as database
instead of DBISAM.
Is there a guide somewhere about this?
What do you consider as the best aproach? Should the create database
statements be taken care of by the application itself (by a first start
routine f.i.) or by the setup process?
Kind regards
TorB.

*****

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> skrev i melding
news:7CE00BBC-488E-4F19-9E31-CF94A84091EF@news.elevatesoft.com...
> Tor,
>
> << A little more complicated than DBISAM... >>
>
> Just different, actually.  If you think of the CREATE DATABASE/ALTER
> DATABASE as the equivalent of setting the TDBISAMDatabase.Directory
> property in DBISAM, you'll see that it is exactly the same process.  The
> only difference is that the EDB path specification for a database is
> persistent in the configuration instead of simply being a property value.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Generally, I would recommend doing your checks on the application startup.
Do you checks for creation or updates on the schema.

Lance

"TorB." <np@datarommet.no> wrote in message
news:1C8B0AA5-03DA-4CDD-AC96-923DA9A34C1B@news.elevatesoft.com...
> Thank you, Tim!
> I can see that now after studying EDB manuals a bit more.
> The case I asked about is working now.
> My main concern now is how to deploy my apps when I use EDB as database
> instead of DBISAM.
> Is there a guide somewhere about this?
> What do you consider as the best aproach? Should the create database
> statements be taken care of by the application itself (by a first start
> routine f.i.) or by the setup process?
> Kind regards
> TorB.
>
> *****
>
> "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> skrev i melding
> news:7CE00BBC-488E-4F19-9E31-CF94A84091EF@news.elevatesoft.com...
>> Tor,
>>
>> << A little more complicated than DBISAM... >>
>>
>> Just different, actually.  If you think of the CREATE DATABASE/ALTER
>> DATABASE as the equivalent of setting the TDBISAMDatabase.Directory
>> property in DBISAM, you'll see that it is exactly the same process.  The
>> only difference is that the EDB path specification for a database is
>> persistent in the configuration instead of simply being a property value.
>>
>> --
>> Tim Young
>> Elevate Software
>> www.elevatesoft.com
>>
>
>
> __________ Information from ESET NOD32 Antivirus, version of virus
> signature database 3993 (20090407) __________
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>


__________ Information from ESET NOD32 Antivirus, version of virus signature database 3993 (20090407) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

Tor,

<< My main concern now is how to deploy my apps when I use EDB as database
instead of DBISAM.  Is there a guide somewhere about this? What do you
consider as the best aproach? Should the create database statements be taken
care of by the application itself (by a first start routine f.i.) or by the
setup process? >>

Creating the database and database objects (tables, views, etc.) at
application startup is always a good option because it makes your
application self-adapting.  If you look at the CDCollector example
application that comes with EDB, you will see that it shows you how to
create the database on the fly at application startup.  The applicable code
is in the data.pas data module unit.

--
Tim Young
Elevate Software
www.elevatesoft.com