+1 for Walter's handling of connections. Wireless devices always are subject to unexpected disconnection apart from sleeping, whether it be a dead spot in a hospital basement, an elevator, a subway, a corridor that goes past the RF maelstrom of the backup generator room..

Others recommend background connection pooling so you can create a connection with every hit without penalty, but that still doesn't solve the issue of lost connectivity when the user presses Save. Future development flavors du jour will silently cache data locally until the connection is re-established and people will have to make haste slowly, accepting that apps behave more like a txt message conversation than a phone call. ;-) Ironically, the ancient txt message and email is better attuned to disconnected transaction success than a lot of "modern" database app development systems.