That makes a lot of sense to me. Not that you don't know the things I am about to suggest, Cameron, but I am going to say it anyway in case other people are listening...
You need to be very careful with your Web db changes, though and track them so that you can run a SQL script that can make changes to the AIR db based upon the "last updated" date inside the AIR db. It is pretty simple to do, but if you lose track, you're screwed. And you need to make sure to avoid collisions with data that they user may be able to change/add to the AIR db. Also, it wouldn't hurt to be able to create a tool that creates your AIR db dynamically (on the server?) and then dynamically package it (on the server?) so that your downloadable .air file can always be up to date. That will cut down on immediate, first-timer updates a great deal. Let us know how this goes for you. I would love to learn from your experience. Leif On Tue, Apr 1, 2008 at 4:52 PM, Cameron Childress <[EMAIL PROTECTED]> wrote: > My best idea right now is to 1) preload a .db in the AIR app 2) query > that DB for the record with the latest "last modified date" and 3) > callback to the server for any deltas since the .db was created, based > on that lastmod date. > > ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
