We've had a Delphi application running on a number of client machines on a customer site for about 4 years now.
This works against both Paradox tables and an Interbase database on the network server.
All of a sudden - one of these client machines is causing us a problem.
The application appears to be failing due to something in regards to the Interbase database.
Each of the client machines has had the BDE installed on it.
Both the Paradox and Interbase aliases have been checked through the 'BDE Administrator' tool - and both open correctly.
Furthermore the 'Database Desktop' application has also been run from this client machine - and the tables can be opened and viewed correctly.
Their main business application fails to open on this one machine (but continues to work on all others on site).
This gives a Windows error message prompting the 'Send / Don't Send' options - but provides little further clues.
There was a mention of the 'kernal.dll' seen when viewing these messages.
This client machine has been restarted a number of times but suffers from the same problem.
A smaller application on this same machine that uses only the Paradox alias operates successfully without error.
Another small application runs a single database update via both the Paradox and Interbase aliases in turn. The first of these against the Paradox alias operates fine - but fails against the Interbase alias / database/
As such the finger of blame is pointed at this.
Has anyone else seen issues like this?
The client machine is quite a new one (and relatively high specc'ed).
My only thought is to reinstall the BDE - but don't know if anyone else has any other ideas?
Thanks in advance.
Steve
This works against both Paradox tables and an Interbase database on the network server.
All of a sudden - one of these client machines is causing us a problem.
The application appears to be failing due to something in regards to the Interbase database.
Each of the client machines has had the BDE installed on it.
Both the Paradox and Interbase aliases have been checked through the 'BDE Administrator' tool - and both open correctly.
Furthermore the 'Database Desktop' application has also been run from this client machine - and the tables can be opened and viewed correctly.
Their main business application fails to open on this one machine (but continues to work on all others on site).
This gives a Windows error message prompting the 'Send / Don't Send' options - but provides little further clues.
There was a mention of the 'kernal.dll' seen when viewing these messages.
This client machine has been restarted a number of times but suffers from the same problem.
A smaller application on this same machine that uses only the Paradox alias operates successfully without error.
Another small application runs a single database update via both the Paradox and Interbase aliases in turn. The first of these against the Paradox alias operates fine - but fails against the Interbase alias / database/
As such the finger of blame is pointed at this.
Has anyone else seen issues like this?
The client machine is quite a new one (and relatively high specc'ed).
My only thought is to reinstall the BDE - but don't know if anyone else has any other ideas?
Thanks in advance.
Steve
