Reflect changes in table to other users immediately.

I'm assuming this is a desktop app rather than browser-based. It would be helpful if you would confirm that. From your question, it sounds like there's one table whose contents are displayed to multiple users simultaneously, and some/all of those users can add / delete / update rows in that table. How are you dealing with cases where a row in the process of being modified by one user is deleted by another? What if two users concurrently make changes to the same row, but different columns? I suspect you may have much bigger problems than how to refresh the screen automatically unless you've addressed these issues. To update the screen(s) on any data update, there are essentially two options: (1) Polling - each client periodically re-checks some d/b indicator to see if anything's been updated, and if it has, refresh the screen; or (2) Push notifications - the process of updating a row pushes out notifications to each client to tell them something has changed. Your choice will depend on various things - just how "immediate" do changes need to be reflected; how often are changes made; is your app the only way that data can be changed; how many clients are there; are all clients on the same network; and probably many other considerations too.
You say you've tried re-fetching the dataset on every change, but your comment suggests you think that refreshing one user's screen will somehow refresh all the others? Regardless, I still suspect you will run into problems if you are just continuously showing a static dataset to all users while allowing any user to update the data at any time.
Go back and think about your users' requirements and how your overall design could fulfil those.