OK, I have NOT tried this myself, but... I swear that there was talk about this else where. If I had time today, I would try this myself on one of my AIR projects, but I have bugs to stomp. I believe that you can create a .db file, package it up in the AIR package, and on first start-up move that file into preferred place on the user's system.
Then, if there are changes to the database you can update your db and re-create your AIR file. For files already deployed, you can set up a way to sync the database. Does that make sense? Can someone confirm that this is the proper way to deal with preloading databases? Leif ------------------------------------------------------------- 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 -------------------------------------------------------------
