Articulate SWFs and absolute paths

Hello everyone.

I'm sure that I am not the only one this has happened to, and am curious how others handle this.

We have a directory standard as follows :

COURSE_NAME

+---PPT

+---FLA

+---SWF

+---Quizmaker

+---Engage

+---Audio

+---Published

Our development team will create a course and publish it.

Later I may need to edit that course, I may take a copy of that entire structure and bring it to my local machine.

I keep the same Directory structure, but when I go to publish it, I sometimes run into issue b/c the Base paths of the original SWFs are different.

Ie - the dev team may be using the dir E:\whatever\COURSE_NAME

I bring it to my local machine and the base directory maybe :

C:\whatever\Version_2\COURSE_NAME

(This is just an example, obviously version control is compromised, but that's outside the scope for this discussion)

This is also an issue when we sometimes deliver full source to our customer and they need to make a chance.

Is there anyway to set up Articulate to use relative paths?  Or can anyone chime in on how they currently handle this?

Ideally it would be great to be able to set up a Project Root and have things based off of that.

So one person can set his root to whatever, can pass the files to someone else and they can just change their root and everything just works.

Any idea or suggestions would be great.