This is actually a rather interesting error as on first examination it looks like it should not happen and why it is happening is not at all obvious.
This is what does the damage. The second New1!
imgMve.New1(imgObj.Value,"MouseMove")
imgMve.New1(imgObj.Value,"MouseMove")
When the event is raised the Data property of imgMve is empty - which does not seem possible as an imgMve object explicitly sets Data immediately before raising the event!
We actually have two imgMve objects now, both wired to the Form MouseMove event and both calling the imgMve_NewEvent event Sub. The first imgMve object is in fact "floating free" as Basic4ppc only has a reference to the second object, that having replaced the first. But it is the original imgMve object defined that raises the event first (having set its Data property) but Basic4ppc calls the second (and only one it knows about) imgMve object which has not yet been called by the Form MouseMove event and so has not yet set its' Data property, hence the error.
@Erel - remember this thread about removing events
http://www.b4x.com/forum/beta-versions/2918-event-difference-between-ide-optimised.html