Hello,
I have a somewhat complex report that, when run directly on the database server takes approx 4:30 minutes
The same report, when launched from another PC over 1gbit LAN, takes 3:45 minutes (surprising, yes).

Now the moment I have the program launched on both those PCs, the one on the server is idle (that is, logged in but not making any requests or traffic), while the one connected by LAN is requesting this same report.

The report now takes around 40 minutes.

I'm not using client server due to certain restrictions.

I've tried setting the session lock method to optimistic instead of pessimistic, but no change.
I also went over the global file IO buffering page, one setting prevented me to log in as multi user.

Any suggestions that would help reduce this overhead when 2 users are connected?
Thanks!

Fady


>I have a somewhat complex report that, when run directly on the database server takes approx 4:30 minutes
>The same report, when launched from another PC over 1gbit LAN, takes 3:45 minutes (surprising, yes).

Not really, there are two many variables. A complex report suggests there could be temporary result sets being created and stored and where depends on how you have your temp storage set, then there's buffering, and the power of the PC as well as any other programs running eg anti virus.


>Now the moment I have the program launched on both those PCs, the one on the server is idle (that is, logged in but not making any requests or traffic), while the one connected by LAN is requesting this same report.
>
>The report now takes around 40 minutes.

Probably due to Windows locking as soon as you go multi user.  I can'r remember the exact term but its mentioned quite a lot on both the ElevateDB and DBISAM newsgroups.

Roy