The "thick" client approach is suitable for screen-intensive applications with interactive data entry. Such applications would suffer performance degradation if processing were performed on a server and passed across the network. By keeping interactive applications on the client, network traffic can be kept at a minimum.
You might also consider this arrangement if you want your client application to interact with other desktop software using the client's processor.