I am having a problem within an application I am developing with TQuery.
The TQuery is created at runtime, SQL statements set, and then opened.
It accesses a PDox table on our network server.

Problem is that one of my users is getting an "Invalid floating point
operation" during the execution of the query. Other users, accessing the
same query don't get the error message (ie: every thing works as it
should).

Everyone has the exact same version of the BDE and of my program.

Anyone have any idea what is going on here?

Thanks in advance for the help.
Greg

Check out that session.privateDir is correctly set to a local drive path
--

Damien.Thouve...@wanadoo.fr
Delphi, C/C++, Oracle developper _ Borland tech partner _ french
____________________________________________________________________

              />
             //     The purpose of software engineering
     (//////[O]>=========================================-
             \\   is to manage complexity, not to create it.
              \>
____________________________________________________________________

I've only seen this problem when a TDateTime field (used in the query)
is stored as a number in a Paradox table and the field is corrupted in
the table (not sure how corrupted but when viewed with Database
Desktop or Paradox all you see is ***************).

This was on a NT 4.0 server with Intel Etherexpress 100B adapters.
Problems are gone (I hope) with Service Pack 2 and the latest adapter
drivers (first ones were so bad they didn't even pass their self test
25% of the time).

The error does not appear trapable with Try... logic.  We normally
just delete or repair the record with the problem.  

This is the symptom of a terrible bug in the 32-bit BDE!
You can get this "Invalid floating point operation" error
if you query an *empty* Paradox table. There is no way
to avoid it except to add code that first checks the number of
records in the table, and then queries only if there are any records.
Yes, it is terrible. Maybe later BDE versions have it fixed.
The bug is at least there in the BDE that came with Delphi 2.0.

Matthias Bollger