On Mar 14, 2007, at 10:12 AM, Jeff Johnson wrote:
> I have commercial VFP applications where the source is held in
> escrow and
> the applications are distributed as an .exe using FoxPro and ms Sql
> Server
> tables. When moving to Dabo what would you recommend for the
> preferred SQL
> Server in my situation? Especially with regard to licensing.
>
> MySQL, Firebird, PostgreSQL, or SQLite?
Unless this is a single-user app, or one with limited demands that
could be met with a file-based DBF approach, don't use SQLite as your
main backend. It is a great package, but it has the same shortcomings
of any file-based system: anyone using it must have read-write access
to the directory in which it is located. If security is not an issue,
and the users limited, SQLite might be the answer, but it generally
wouldn't be my first choice for a robust, high-volume server.
PostgreSQL seems to be the best balance of speed, power, ease-of-use
and licensing. MySQL is great to work with and extremely fast, but if
you are distributing an app that uses MySQL, you start to run into
licensing issues. Postgres doesn't have that problem.
I don't know enough about Firebird to comment. It seems to be full-
featured, but seems to have the oddest quirks, too. I think if you
know what they are you can avoid them, but my impression is that this
would have the longest learning curve.
BTW, I always did my VFP apps with a MySQL backend for the main
data, but kept a lot of local stuff (config settings, etc.) in DBFs,
since that was much handier. You can do the same with SQLite: use a
server for the main backend, but use SQLite to store local stuff.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
