Roy,

<< It opens just fine. Same in Delphi, for example in the Fields Editor. On
a second computer, the application also works just fine. >>

Something is not right here (obviously .   If the table opens fine in
Delphi and the EDB Manager, then the only way that it would not open fine at
runtime is if the configuration path has changed at runtime or the database
path has changed at runtime.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:9AB5FECD-0B49-4D74-91EB-7EB63F24DEC7@news.elevatesoft.com...
> Roy,
>
> << It opens just fine. Same in Delphi, for example in the Fields Editor.
> On a second computer, the application also works just fine. >>
>
> Something is not right here (obviously .   If the table opens fine in
> Delphi and the EDB Manager, then the only way that it would not open fine
> at runtime is if the configuration path has changed at runtime or the
> database path has changed at runtime.
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com

The configuration path is definitely the same. We do not reach the point
where the database path is relevant, as the crash occurs as soon as the
session gets connected.

We started on computer 1 (all running ok), then copied exe, cfg and data to
computer 2, and this is where we cannot get it going. Then exe, cfg and data
were copied in the same way to computer 3, and ... no problems at all.
Running fine.

We are now uninstalling the whole EDB from computer 2, and re-installing.
See if that helps.

RJ

Roy,

<< We started on computer 1 (all running ok), then copied exe, cfg and data
to computer 2, and this is where we cannot get it going. Then exe, cfg and
data were copied in the same way to computer 3, and ... no problems at all.
Running fine. >>

And computer 2 has the necessary directories present to support the
definitions in the configuration file along with the configuration path
itself ?

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:FB700A9D-12F1-469D-BE57-5848B0B691F4@news.elevatesoft.com...
> Roy,
>
> << We started on computer 1 (all running ok), then copied exe, cfg and
> data to computer 2, and this is where we cannot get it going. Then exe,
> cfg and data were copied in the same way to computer 3, and ... no
> problems at all.
> Running fine. >>
>
> And computer 2 has the necessary directories present to support the
> definitions in the configuration file along with the configuration path
> itself ?
>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com

All in place, but ... we reinstalled the whole EDB, and it is now all
working fine. No idea what went wrong, and no longer any way to find out. At
least we are on our way again. Thanks for the help!

Roy,

<< All in place, but ... we reinstalled the whole EDB, and it is now all
working fine. No idea what went wrong, and no longer any way to find out. At
least we are on our way again. Thanks for the help! >>

Wow, that's really odd.  I suspect that the issue might have been a bad
configuration file on the computer in question.  But, no worries, all is
well.

--
Tim Young
Elevate Software
www.elevatesoft.com