thus spake val_melamed :

> I generally disagree with the statement "Firebird is a client/server

> database and you should work with datasets only containing records

> and fields that you're currently working on". I would put the

> *embedded* Firebird in the same class, as far as how it gets used,

> with Access, FoxPro, etc. desktop database engines.

When this thread first started, it seemed to me that there was a fundamental miscommunication between the parties, which led to the initial exchange being... well, unfriendly. Val and Adam are now having a productive conversation, and I have little to add... except that I thought of an analogy that I like so well that I can't keep it to myself.

A fire has broken out on your property (whatever problem it is that your application solves). There's a fire hydrant (your data) in front of the house, but you don't have the special wrench to open it. So you call the fire department (Firebird) - but when they arrive and open the hydrant, you say "No need for the hose, guys, I've got all these buckets!" And your initial question - about reducing the cache size - is like saying "You know, we're not using this hose reel - could we move it out of the way of the bucket brigade?" Stretching my analogy to its breaking point, it now appears (from your later explanation) that the fire is limited to one small doghouse, and that the bucket brigade is perfectly adequate. But the reason your initial question got shot down the way it did is that a lot of the people on this list are volunteer firemen, who (in the words of the Beatles) "like to keep their fire engine clean - it's a clean machine..."

Again, I have no technical contribution to make, and I'm sorry for intruding. But I really liked my analogy, and I hope you did too...





____________________________________________________________________________________
Yahoo! Music Unlimited
Access over 1 million songs.
http://music.yahoo.com/unlimited