Without built in support of jQuery you can't really do anything to prevent another module, etc from registering jQuery... that is why you register it using a different namespace etc the way I showed... you can name that parameter anything you want "mySuperJQueryLink" etc, so if you made it unique and somebody else was loading it up you'd have the jQuery linked in a few times (unfortunately), but at least not conflicting.

On that same note, as a core enhancement of course this would "fix" the problem, but where they have their own javascript libraries for webutility, etc, I can't really see them including core support of the jQuery library (maybe I'm wrong, but just venturing a guess).

Thanks for the replays,

At least i can solve my problem in the meanwhile.

Many thanks

This works well for me so far:

<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.2.6/jquery.min.js"></script>

<script type="text/javascript">

jQuery(document).ready(function(){
        jQuery.noConflict();
    });

</script>

Looking forward to having full jQuery support in 5.0 though!

Take care,

Ian