New Zeal,
I know you said that the uc_event does not work for all versions of ubercart. It turns out that upgrading to ubercart-5.x-1.3 did not fix the:

warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'uc_product_add_to_cart_form_6' was given in /var/www/htdocs/includes/form.inc on line 218

The code that should be patched is now at line 1918. If I apply the patch, the error message remains.
Previous paid event content using ubercart-5.x-1.0-rc2 (which works perfectly) loses the Add to cart' button though all other information remains and the warning is shown.
Now, creation of a new event gives all fields as in the ubercart-5.x-1.0-rc2 before save.
On hitting Add to store, everything is fine so far (no message).
On submit, the message shows up again and no 'Add to cart'.
The above is with patch applied at 1918.
If I remove the patch, same as above. (ie no difference with or without patch at 1918 - that should be weird right?)
By the way, in this case I'm using uc_event_0.zip and not uc_event.zip
Anyway. So I stick with the downgrade ubercart. Anything am missing or risking? If so, can you maybe guide us again on the way foward for the ubercart upgrade? Please?

Further (bear with me), I originally tied to use the openresort module with e-commerce because what I am trying to achieve is make reservations but not for rooms. I need to make reservations for tours. That particular module, though it kinda worked was a whole can of worms and is not as flexible as uc_event.
Thing is guy, I can now make bookings (kinda) for a tour/safari using your module. But, now away from ubercart since you have that fixed, what can be done in regards to event in order to allow me to work the following scenario:
I have say 5 events with variable length (number of days) (5, 7, 10 etc)
Allow payment for more people in a group to a particular event.
Allow combination of events.
Here's the catch (reason why I tried to go with the openresort module for booking):
Event start dates are not fixed and depend on the user. The number of days is whats fixed.
Meaning (I guess) that:
-I create a generic event that is always open (with the condition that start date must be 30 days away from current date.
-The user then edits the date part of the event (in uc_event?) in that he clicks on my event but instead of being taken to it, all the data from my event is loaded. He can only see the date fields which he is actually editing while to the user it looks like a date booking (get?).
This new event then gets pushed to ubercart. Once ubercart finishes with it, it is deleted from the site (or maybe stored for the user only?) The original remains intact (since its just a loader link for my fixed info that will allow the user to change the date).
In essence, the user creates an event that he pays for with my pre-loaded info on cost and his date (but my number of days).....hmmmm
Am I making any sense?
Is it possible?
I know zilch about php coding but I swear I can see the logic flow.

TThanks New Zeal, thanks ambereyes, for the module.