Handling Service Disconnection - Queuing Calls

I posted another question recently about a problem i was having with some pattern code, and it was suggested to me that i might not be using the correct pattern to solve my problem in the first place, as such i thought i would post this question.

The problem i'm trying to solve is such:

I have a WPF client that will be run from remote offices, it's pretty simple handling data entry and editing, they connect to WCF services hosted at our end (before going to a DB). The problem is that the client connection is unreliable and can drop out constantly.

So, my idea was to use the command pattern, and queue the command (such as update, delete) and when the connection returns execute the commands.

However, it was suggested that the command pattern might not be a good fit here. So my questions would be:

Is the command pattern a good match? If not, why?