Igor Korot wrote:
Darren,
On Tue, Oct 23, 2012 at 8:53 PM, Darren Duncan <dar...@darrenduncan.net> wrote:
You should not have an application installer, at all. Instead, you can ask
the question on where to store the database when the user opens your
program. Or better yet, your application should have menu commands like
"new database" and "open database", where if they choose the former then you
ask them (using Apple's standard method) where that database goes. If they
chose "open database", then you can let them open an existing one, or one
should be able to double-click the database file in the Finder to open that
one instead, which is what Mac users expect. As such, your application
should support having multiple databases per user, even if they may
typically just use one. If users open your program directly and not by
double-clicking on a database file, you could automatically bring up a
prompt to make a new one, as if they used the "new database" menu. -- Darren
Duncan
I doubt the user of the application will wait couple of minutes while
the database
will be created and the data will be populated for about 5000 records.
They won't come from the internet and I'm planning to insert them as a bulk
procedure from the Excel file I have.
Thank you.
Why would it take that long? Creating a database with 5000 records on a modern
machine shouldn't take more than about 1 second or so. But even if it takes
longer, my comment is about letting the user choose from the application itself
where the data they edit goes, and your comments about the user waiting have
nothing to say against that. -- Darren Duncan
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
