It pops up once in a while when, for instance, I try to add a field to
a table. Config path is, of course, not empty. When I go to the
datamodule that contains the dbengine component and then switch back to
the datamodule that contains the concerned table and try to add the
field again, the error disappears.

Just reporting this oddity.

Dominique

>It pops up once in a while when, for instance, I try to add a field to
>a table. Config path is, of course, not empty. When I go to the
>datamodule that contains the dbengine component and then switch back to
>the datamodule that contains the concerned table and try to add the
>field again, the error disappears.
>
>Just reporting this oddity.

I used to get something similar to this back with DBISAM and D6. I found the solution was to open the "master" datamodule first. Until you do stuff isn't initialised so what will be happening in your case is that the table will be trying to use the default session/engine. Just a guess of course.

Roy Lambert [Team Elevate]

Roy Lambert wrote:
> I used to get something similar to this back with DBISAM and D6. I
> found the solution was to open the "master" datamodule first. Until
> you do stuff isn't initialised so what will be happening in your case
> is that the table will be trying to use the default session/engine.
> Just a guess of course.

Problem is that when I then close the IDE and start it up again, it
gives me a handful of these. Odd. Only happens when I visit this
datamodule and fiddle around with a table.

Dominique

>Problem is that when I then close the IDE and start it up again, it
>gives me a handful of these. Odd. Only happens when I visit this
>datamodule and fiddle around with a table.

What happens if you just open the master datamodule BEFORE you open any other forms / datamodules in the project?

Roy Lambert [Team Elevate]

Roy Lambert wrote:
> What happens if you just open the master datamodule BEFORE you open
> any other forms / datamodules in the project?

I'll have to check. At the moment I'm just clicking through all the
config path errors during start-up each day...