It sounds like the problem isn't the program per se but the available memory (including hard disk space) on server or the transport speed of your network connection. Whether the report is run from your machine or the server the actual process is going on on your client machine and the server is actually onlys sending the data table information to paradox upon request. It sounds like the server is having problems sending the data files in a responsive manner. Another issue could be that on the network since the database is shared, if the report is query based than people working on the database could be initiating and releasing locks as well as changing data. The query could be set to restart upon change s to the underlying table which would not occur if the dat is first transferred locally. The change in the table would restart the query regardless of whether the change affected the data in the report.