Question about Client Networking 1

[PPettit]

Can someone explain to me what Client Networking is for?

The other day, I was trying to build a report in "RESULTS". When I ran it, the report bogged down my server for a very long time (over 30 minutes). I guess my report wasn't set up right and it was trying to search through/return too many records. I called the vendor to see if there was a graceful way to terminate the report without crashing the database. The support guy just ended up killing my Terminal Server (Windows Server 2003 Enterprise edition) session. As expected (by me), this crashed the database. The support guy was surprised that this happened and started poking around and said that we were missing the "Client Networking" module which would have prevented the slowdown and/or crash. I don't have a lot of faith or trust in our vendor, so I was wondering if someone else could tell me if this is true. I don't want to get stuck paying for something that I really don't need.

If someone could at least provide a link to some info regarding Client Networking, that would help out a lot. So far, I haven't been able to find anything that describes it's features/benefits.

 

[tonys123]

The Progress Client Networking product is the bit you need to run a Progress application in client-server mode. With the Client Network licence, you also get the drivers needed for ODBS access to your database. With regard to why your DB crashed when the Results session was terminated, that is not, in my opinion (and we have been developing in Progress for about 15 years), anything to do with the lack of a Client Network licence. Similarly, Client Networking wouldn't have made your Results report run any faster - it was slow because the query you wrote was probably inefficient and didn't use indexed fields in the search.

 

[PPettit]

Thanks for the info.