Since an AIR SQLite database is just a file on the filesystem, the easiest way to back it up is to just copy the file to somewhere else. You’ll want to do that when the database connection is closed to make sure the database isn’t in the middle of a transaction.

As for using MySQL with Adobe AIR, most often you’ll do that with a MySQL database that’s hosted on a server on the web somewhere. You’ll use some sort of server middleware like PHP, ColdFusion, etc. to go between your AIR app and the database. This is exactly the same as how you would use MySQL with any Flex or Flash app, so you should be able to find plenty of resources online. (I did a presentation on this several years ago. The concepts are the same, but a fair amount has changed since then in terms of actual implementation so you’ll probably want to look for a more recent tutorial.)

Some people have wanted to use MySQL running on a user’s local machine as a data source for an AIR app without needing a middle-tier. This was mostly in the early alpha days before the SQLite functionality was added, but the assql (http://code.google.com/p/assql/) project attempts to support that workflow.

There are some important differences between working with databases in synchronous versus asynchronous mode. Some things “just work” when you switch between them but I’m not surprised that for a whole application it doesn’t work.

If you’d like to see a comparison between the two or see examples of using synchronous execution, you might want to take a look at these two examples/articles I wrote for the Adobe Developer Center. They are identical except that one uses synchronous execution and one uses asynch:

Working asynchronously with a local SQL database
Working synchronously with a local SQL database

However, I would also recommend that you give some thought to the question of why you want to use synchronous instead of asynchronous execution. For simple things synch code is easier to write and smaller. However, once you get to “real world” levels of complexity the benefits of using synch execution quickly disappear compared to the downsides, and you’ll likely end up rewriting your code using asynch anyway.

That’s one of the reasons I created my “SQLRunner” library — it removes a lot of the pain of the asynch approach (the many event handlers that are required for most actions) so you can execute your SQL in just a couple of lines of code and still get the benefits of using asynch execution, reusing objects, etc.

Hope this helps.

Since this project is really intended as an example application (i.e. as source code you can look at) I didn’t bother providing a .air file for installing it.

If you want to test the application, you can compile it using the Flex SDK or Flex Builder and try it out. You can also use either one of those tools to create a .air file that you can install (assuming you have the AIR runtime installed on your machine).

Plz do assist me ASAP.

regards,