Actually not that large by today's standards -- just in the low megabytes (<10 Mb I'd guess). The reason for the uncertainty is that it entirely depends on how much data the user has in their original database, which can vary widely.
I can understand the web server solution, and of course I already have my own business web server, but I was hoping to avoid having to build my own web-based solution. Such a solution would have to include user- specific login protection (name/password, etc.) since these files can contain private information and I'd have to make sure that the files would be fairly secure from unauthorized downloads and other hacking attempts. But I've done plenty of PHP scripting before... On Jul 26, 7:46 pm, greg <[email protected]> wrote: > Before you jump to the offered solutions, it might be helpful to > momentarily back up and define what you mean by "rather large". For > example, are your data files 1 GB compressed? > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
