on 2006-02-22 4:32 AM, Simon Forster at email@hidden wrote:
> Matt Neuburg is somewhat scathing as to its
> capabilities.
My take is that it's a matter of expectations. In general, you should try to
scale the solution to your objectives.
If you need a very simple data store to manage and retrieve modest amounts
of data between runs of your script, Database Events is perfect. It's much
easier than the old way (using the File Read/Write commands to build your
own text-based data store), both for storing new data and for retrieving it.
For this purpose, the standard default location used by Database Events to
store the data is an advantage, because it frees you from the need to manage
file saves.
But if you need more complex database capabilities, and especially if your
data may be accessed both by scripts and by other means, then Matt is
clearly right in suggesting that you cannot expect Database Events to meet
that need.
I don't know whether other AppleScript-related database solutions, such as
the one suggested by Matt, are as simple to use as Database Events for
simple tasks. I haven't tried them.
--
Bill Cheeseman - email@hidden
Quechee Software, Quechee, Vermont, USA
http://www.quecheesoftware.com
PreFab Software - http://www.prefab.com/scripting.html
The AppleScript Sourcebook - http://www.AppleScriptSourcebook.com
Vermont Recipes - http://www.stepwise.com/Articles/VermontRecipes
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/applescript-users/email@hidden
This email sent to email@hidden
