>I have created an executable and distributed it to the customer. Upon installation, the customer complains about how painfully slow the application is. I am thinking... 2 seconds to perform multiple saves and return control is slow??? What the reality is... at the customer site it will take close to 30 or more seconds to perform a save.
>

You need to look at things like network collisions.
Here are some ideas:
Try just copying a large file from the server to a workstation and timing the result.
Do this on both your clients network and the network where your application performs well.
If the network card supports “opportunistic record locking”, try turning it off. Also try setting the network card to half duplex instead of full and even forcing the network card to 10 megabit instead of 100.
There may be some old CAT 3 cable with machines on it having their network card setup to auto negotiate.
They will agree on 100 but they will be resending packets all the time due to the poor cable.
They may be using hubs instead of network switches. This will make for much more network traffic than necessary.
I would guess that it's not a traffic issue as much as a network collision or segmenting issue.