I have an application built with Delphi 5 and DBISAM v3.3 CS running OK at a client's site.

The app uses TTables and an Infopower 4000 TwwFilterDialog to filter tables in a grid.
Everything is fine when the DBSrvr is on the same machine as the EXE. As soon as I move
the DBSrvr to a different machine the app will close when the FilterDialog is invoked.
Everything else works fine and the network cables, connections, cards have been run
through the wringer.

Is there anything anyone can think of that would change when the DBSrvr is moved to a
different machine that would cause this kind of behavior?

I had an older version of this app running fine on v3.3 CS, WITH the TwwFilterDialog AND
DBSrvr on a dedicated machine. Never had a problem. It's just this new build that is
driving me crazy. I ASSume it's a really stupid error on my part but I can't figure out
where to look.

Thanks in advance for any suggestions.


Norman

Norman,

<< The app uses TTables and an Infopower 4000 TwwFilterDialog to filter
tables in a grid. Everything is fine when the DBSrvr is on the same machine
as the EXE. As soon as I move the DBSrvr to a different machine the app will
close when the FilterDialog is invoked. Everything else works fine and the
network cables, connections, cards have been run through the wringer. >>

This definitely sounds like a hardware/environmental issue.  You're not even
seeing an error message from DBISAM or the Winsock layer, which is what
normally occurs when you have a network issue.

You didn't set up the application to terminate when it received an exception
in the Application.OnException event handler, correct ?

--
Tim Young
Elevate Software
www.elevatesoft.com