> better to go with SQLite. Its cross platform and well proven. I think
> Firebird will give you that too, though I have never used it.
>
Firebird is a great option, cross platform, it can work like access
without any server running, using embedded mode to a full blown server
which can handle t
If you are going to go with Python, don't include Access in the mix at all.
If you want a small light-weight, serverless database back-end, you would be
better to go with SQLite. Its cross platform and well proven. I think
Firebird will give you that too, though I have never used it.
Most peop
On Jul 15, 2005, at 11:19 PM, William Lodge wrote:
> Finally, does anybody know of any Web sites having examples of
> database apps
> in Python?
You might want to look at Dabo, which is a database application
framework for Python. In about 30 seconds you can create an application
that
On Sun, 2005-07-17 at 01:30 +0200, Johannes Findeisen wrote:
> My recommendation:
>
> Use Python! You will love me in some years because i have said this.
> When using Access you are binding your application to Microsoft. You
> need a runtime version of Access when distributing the application to
On Fri, 2005-07-15 at 23:19 -0400, William Lodge wrote:
> I'm at a loss on how to compare Python vs. Access VBA for a database
> project. I'm estimating 20 tables and several forms and reports. Some of the
> tables could grow to many thousands of rows w/i a year or so. The app would
> be resident o
