Avoid Child Package version conflicts

[MDXer]

I know this issue has hit me more than once. While researching another issue I was having I came across a tip somehwere (sorry read so many resources I don't remember), that had an excellent solution to the problem of an execute_package_task being mapped to an older version after you have modified the child package.

The fix is to do a disconnected edit and then edit the PackageID property and deleting the GUID. This will force the package to execute the most recent version based upon name.

Shoot Me! Shoot Me NOW!!!
- Daffy Duck