Problems with data in cache

Hello everyone,
I have a database server running Firebird 1.5 SS under SUSE Linux 8.0, and a software that access this server from many client machines. This would be a multiuser software, so, each user has its own database user created. But I've been having a problem with data refreshing, and I believe it's because this data is in cache. What happens is:

If a user is logged in the software from a machine, and alters data in a table... a second user, who was already logged in the software before the data chance, will not see this alterations. When he fetchs the data, he'll receive the old data, and not the altered data. He'll only be able to see the altered data after he logs out and logs in again. In other words: after another connection is made.

I figured this would be a cache problem, so I did a little research on the web and even changed a parameter in the firebird.conf file... the number of cached pages was 2048 and I changed it to 50, but it didn't solve my problem.

I'd like to know if any of you have already seen this problem... is there any way I can disable the data caching? Is there any way I can make it fetch data always from the database and never from the cache, even if it will slow down my application?

Thanks for your attention...

Are you shure that a commit from the first user is issued?

I've just checked. Yes, there is a commit.

Anyone?

Other clients need to refresh - that's it.
Desktop databases generally handle this for you in the background (Paradox does and Access after a fashion) but with SQL your app needs to either monitor for changes (use firebird events not a good idea if you have many clients) or perform refreshes at some determined interval or event.

Put your cache back up to it's original size as soon as possible. Remember that the cache is ONLY for the FB server - effectively anything in cache is in the database.

Mick