Hi, thx for the good replies.
I'm using a MSSQL 2005 DB so if you know some "watcher" class in .NET that monitors changes I can understand that would be a better solution. It's something I didn't thought of, thx!
And gbianchi, why would that be a painfull thing on a heavly loaded server? That's indeed an important issue for me cause this server runs our product (a webappliaction) for track and trace so nothing can go wrong on that server otherwise we loose incomming messages from the black boxes and you can imagine this NOT being what we want :)

I am jumping in the middle of this and not grasping what is trying to happen here but usually when I want my page to come back and update data later that is still being process, I do it in AJAX asynchronously. This way I can grey out the area that will retrieve the data and usually show an animated gif of loading that will go away once the data is available and populated to the appropriate fields.

Yes, that seemed indeed a good solution.
I've seen very little of AJAX but its possibilities are wide and various.
But I'm just off school since this year and honestly, I'm not so good YET :p.
So I reserve learning AJAX for after I mastered most of the .NET 2.0
but I the more I learn the more it's obvious that sooner than later I have to learn AJAX.
I'm waiting the response of my boss (head programmer) to let you guys know what I finally use as solution.

Cheers