I have "copied" code fron CD Collector demo to change database path to
config file. I get following error message when starting exe file :

"Elevate DB error #401 The Table or View Databses does not exist"

What's wrong?

I have following code in datamodule :

---
with qryDBSetUp do
   begin
     SQL.Text := 'SELECT * FROM Databases WHERE Name = '+
Engine.QuotedSQLStr('ToDo');
     Open;

     if (RecordCount=0) then
       begin
         Close;
         SQL.Text:='ALTER DATABASE "ToDo" PATH '+
Engine.QuotedSQLStr(ExtractFilePath(Application.ExeName)+'data');
         ExecSQL;
       end
    else
     Close;
   end;
---

Thanks,

-mikko

Mikko,

<< "Elevate DB error #401 The Table or View Databses does not exist" >>

Is that error message correct, or did you mis-type the word "Databses" ?  If
the latter, then you need to make sure that the qryDBSetUp query is using
the Configuration database as its active database via the DatabaseName
property.  You can only query the Databases table via the Configuration
database.  You could also use this, if you wanted:

with qryDBSetUp do
   begin
     SQL.Text := 'SELECT * FROM Configuration.Databases WHERE Name = '+
Engine.QuotedSQLStr('ToDo');

....


--
Tim Young
Elevate Software
www.elevatesoft.com

Jep, i mis-typed word "Databases".

qryDBSetUp uses Configuration database and i also changed SQL to "'SELECT *
FROM Configuration.Databases WHERE Name etc."

Now when i run app from development folder everything goes ok. But when i
move app to another folder and execute it Visual Studio Just-In-Tine
debugger warning dialog opens and app execution is terminated.

-mikko


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> kirjoitti
viestissä:59E856BA-A602-4BF9-93B2-253FEF03A9D5@news.elevatesoft.com...
> Mikko,
>
> << "Elevate DB error #401 The Table or View Databses does not exist" >>
>
> Is that error message correct, or did you mis-type the word "Databses" ?
> If the latter, then you need to make sure that the qryDBSetUp query is
> using the Configuration database as its active database via the
> DatabaseName property.  You can only query the Databases table via the
> Configuration database.  You could also use this, if you wanted:
>
> with qryDBSetUp do
>    begin
>      SQL.Text := 'SELECT * FROM Configuration.Databases WHERE Name = '+
> Engine.QuotedSQLStr('ToDo');
>
> ...
>
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Forget to mention....in same folder where's new folder for app, new folder
with same name as original folder is created.

-mikko



"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> kirjoitti
viestissä:59E856BA-A602-4BF9-93B2-253FEF03A9D5@news.elevatesoft.com...
> Mikko,
>
> << "Elevate DB error #401 The Table or View Databses does not exist" >>
>
> Is that error message correct, or did you mis-type the word "Databses" ?
> If the latter, then you need to make sure that the qryDBSetUp query is
> using the Configuration database as its active database via the
> DatabaseName property.  You can only query the Databases table via the
> Configuration database.  You could also use this, if you wanted:
>
> with qryDBSetUp do
>    begin
>      SQL.Text := 'SELECT * FROM Configuration.Databases WHERE Name = '+
> Engine.QuotedSQLStr('ToDo');
>
> ...
>
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Mikko,

<< Now when i run app from development folder everything goes ok. But when i
move app to another folder and execute it Visual Studio Just-In-Tine
debugger warning dialog opens and app execution is terminated. >>

What is the TEDBEngine.ConfigPath property set to ?  Is it set to a full
path name and not a relative path name ?

--
Tim Young
Elevate Software
www.elevatesoft.com

It's full path name.

-mikko


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> kirjoitti
viestissä:E2B5117B-0380-4B2D-8E37-548E952074F3@news.elevatesoft.com...
> Mikko,
>
> << Now when i run app from development folder everything goes ok. But when
> i move app to another folder and execute it Visual Studio Just-In-Tine
> debugger warning dialog opens and app execution is terminated. >>
>
> What is the TEDBEngine.ConfigPath property set to ?  Is it set to a full
> path name and not a relative path name ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Mikko,

<< It's full path name. >>

Well, I'm stumped.  If you want to send me your application source code, I
can test it here and tell you where you went wrong.   Something is messed up
with your config path or configuration settings.

--
Tim Young
Elevate Software
www.elevatesoft.com

i sent it to support@elevatesoft.com

Thank's, this is very helpful from you.

-mikko

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> kirjoitti
viestissä:2E4A5FCF-EF39-495A-851E-76778799238A@news.elevatesoft.com...
> Mikko,
>
> << It's full path name. >>
>
> Well, I'm stumped.  If you want to send me your application source code, I
> can test it here and tell you where you went wrong.   Something is messed
> up with your config path or configuration settings.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>

Mikko,

<< i sent it to support@elevatesoft.com >>

Thanks.  You've got your queries set to Active at design-time, thus they
will try to access the database prior to the data module create event
getting fired, which is where you are altering the database path to conform
to the current directory information.  Make sure that the TEDBEngine.Active
property is set to False before you compile and distribute your application,
and that should fix the issue.

--
Tim Young
Elevate Software
www.elevatesoft.com

Can we have a property like "IgnoreDesignTimeActivationAtRunTime" or
something like this?

Ralf

Tim Young [Elevate Software] schrieb:
> Mikko,
>
> << i sent it to support@elevatesoft.com >>
>
> Thanks.  You've got your queries set to Active at design-time, thus they
> will try to access the database prior to the data module create event
> getting fired, which is where you are altering the database path to conform
> to the current directory information.  Make sure that the TEDBEngine.Active
> property is set to False before you compile and distribute your application,
> and that should fix the issue.
>