Thanks for the feedback Robax, I hope that it may help Steve.
For information, I have also tested something else: in one page, I have put a simple HTML link with target=_blank
It opens a new window. Then, I have asked some people complaining about the Repository to test this link: everybody manage to open the link, even people with Norton Internet Security or other pop-up killer. Consequently, I think that the main problem concern the way the Repository handles the link. Probably to better track link click, which is essential in the repository, but we must find another solution...

DV

Rob,
Thanks. I am aware of the html solution, and if the repository was just rendering links that would work. The issue that I am faced with is counting the clicks. When a user clicks on a hyperlink, I need to send the click back to the server so it can be recorded. That's the only way I know of to maintain the number of times each link was clicked on. It requires server-side code to increment the click count and store it in the database. Once control is on the server, the only way to continue the process and have a new window open is with javascript. I know of no other way. That is the real dilema here for me. When control remains on the client, ie: the use clicks on a hyperlink and a new window is opened, popup blockers will allow that because it was directly initiated by a user action. However once I introduce a server process ( storing the fact that the link was clicked ) the server has to initiate the process and therfore the popup blockers will block the window.

I looked at the core Links module, and if you set the module settings to open in a new window, I think you'll see the same behavior because the Links module also counts clicks.

Anyways, thanks for the suggestion, but I'm still not aware of a solution. If anyone out there can help, that would be great.