Do you mean that you need to work through a web application even offline? It looks like you need Google Gears or another structured storage of HTML5 implementations.
If you use the native application offline, then yes, it looks like you need a local database too.
Do users know when they are about to disconnect? If so, you can let them "check" a subset of the database that they need, and then "go online" and synchronize. Otherwise, you can synchronize the data that they used recently, but clear the local database that they have not used for a long time.
It is quite difficult how much this will depend on your particular application. For example, multiple users should be able to work with the same set of records, for example?
Jon skeet
source share