Switching Back and Forth Between Microsoft Project and Excel Seamlessly?

Question

My team is using Microsoft Project for a project, but some people we are working with do not want to use Project. Is there a way to go seamlessly back and forth between Project and Excel? Meaning, is there a way for me to take my Project file, convert it to a Excel file, send it to them, have them edit it in Excel, and then have me able to bring their edited Excel information back into Project?

Thank you!

Answer 1

I emailed you. Thank you!

Answer 2

MO_NYC,

Okay, exactly what data are you looking to export, edit and import back to Project? Let's start there.

I recently helped a couple other users with this same type of issue (ref: https://answers.microsoft.com/en-us/msoffice/forum/msoffice\_project-mso\_winother-mso\_2013\_release/ms-project-vba-to-link-excel-values-questions/78f8fd58-a330-424b-9384-afa59567f8be). It may be easier to work one-on-one. You can contact me directly at the address below. I will ask some questions.

John

jmacprojataticlouddotdotcom

(remove obvious redundancies)

Answer 3

Hello Mo

I am a fellow Community member here to help I'm sorry to hear you're having difficulty with this. I know that it can be very frustrating.

I believe the following guide will address the processes that you are looking for.

https://support.office.com/en-ie/article/export...

I do hope that this is helpful to you. Please let me know if I can be of any further assistance I am happy to help in any way I can.

Answer 4

Hi John,

Thank you for getting back to me so quickly! I have been fooling around with VBA but been unsuccessful. I am very interested in the approach though, so any help would be greatly appreciated!

Answer 5

MO_NYC,

You kind of rained on the parade with the word "seamlessly", otherwise the answer would be "yes".

There are basically two methods for transferring data between Project and Excel.

The first involves export/import maps wherein Project data is exported to Excel via an export map, data is edited in Excel, and then the Excel data is imported back into Project. The problem with this approach is that all data is treated as text so it won't always arrive in Excel the way you want and it takes some finessing to get the modified data back to Project the way you need (i.e. not so seamless). However, if the transfer is just for basic data (e.g. actual start/finish, actual work, remaining work, etc.), once the format and maps are ironed out, it can be a viable process.

The second is to use VBA. Although this method is more complex to set up, once it is in place, the transfer both ways can be "seamless". I've used this process on multiple occasions and in my opinion, it is worth the effort since it is more reliable and a lot more flexible. If you are interested in this approach I can help.

Hope this helps.

John