Glad to hear you were able to get it sorted out!
But don't you think it is an issue?
For me it is still unclear why it requires the full path.
When we run macros, they get compiled as a .NET assembly, but the assembly isn't actually a file on the file system anywhere. It's not running under the CF process or anything really related to it, so any external references need to be fully qualified.
Please let us know if you have any further questions at all.
Thanks!