How set Outlook 2010 with the sames VBA as of Outlook 2007
We just purchased a new notebook with WINDOWS 8 Pro and Ms Outlook 2010.
In order to start using our Outlook PST, we just copied the PST to the new notebook.
All seem ok and can access all our emails, notes, tasks and contacts.
The problem is the VBA developed and heavily used in Outlook 2007.
How can we have all VBAs of our previous Outlook 2007 in our new Outlook 2010?
In order to start using our Outlook PST, we just copied the PST to the new notebook.
All seem ok and can access all our emails, notes, tasks and contacts.
The problem is the VBA developed and heavily used in Outlook 2007.
How can we have all VBAs of our previous Outlook 2007 in our new Outlook 2010?
ASKER
We were about to close the question but received your entry.
We resolved the problem.
After days of googling and trial and error, we finally found the answer was super simple: just copy the VBA over to Outlook 2010.
When running, messages of "missing object" started appearing. Again, after a long time searching, it seems the cause was missing files in "Reference".
We compared file in both 2007 and 2010 and copied all missing DLL and OSX, etc. to' 2010.
Everything seems to work fine except 2 or 3 macros (we are still searching).
We would like to get your feedback on your comment of "not advisable"; please advice.
We resolved the problem.
After days of googling and trial and error, we finally found the answer was super simple: just copy the VBA over to Outlook 2010.
When running, messages of "missing object" started appearing. Again, after a long time searching, it seems the cause was missing files in "Reference".
We compared file in both 2007 and 2010 and copied all missing DLL and OSX, etc. to' 2010.
Everything seems to work fine except 2 or 3 macros (we are still searching).
We would like to get your feedback on your comment of "not advisable"; please advice.
Since you are not mentioned, what kind of vba you are going use for outlook 2010,
i commented as 'not advisable', because we need to look up for changes that are made in outlook 2010 before using vba.
Also in your second post you mentioned as "except 2 or 3 macros" and "We are still searching" which is exactly what i tried to say.
Thanks!
Krish.
i commented as 'not advisable', because we need to look up for changes that are made in outlook 2010 before using vba.
Also in your second post you mentioned as "except 2 or 3 macros" and "We are still searching" which is exactly what i tried to say.
Thanks!
Krish.
ASKER
Ok, the answers:
1. "...what kind of vba you are going use for outlook 2010"?
The VBA or macros we want to use in Outlook 2010 are the macros we have been
using in Outlook 2007.
2. "We are still searching"
What we mean is that when copied the Outlook 2007 VBA to Outlook 2010, there
were a seried of problem that the "objects" were not found. We solved almost all
because we copied the DLL/OXC to Outlook 2010 folder.
"We are still searching" is that there is a grid for a VBA we copied that is still
not working.
The macro uses vbaGrid6.ocx ("vbAcceslator Grid Control (VB6 Version)")
Hope to answer your questions.
You mention "we need to look up for changes that are made in outlook 2010 before using vba". Even though we have working 95% of the macros, we would greatly appreciate your feedback on your comment. Maybe we have overlooked something.
Thank you very much.
1. "...what kind of vba you are going use for outlook 2010"?
The VBA or macros we want to use in Outlook 2010 are the macros we have been
using in Outlook 2007.
2. "We are still searching"
What we mean is that when copied the Outlook 2007 VBA to Outlook 2010, there
were a seried of problem that the "objects" were not found. We solved almost all
because we copied the DLL/OXC to Outlook 2010 folder.
"We are still searching" is that there is a grid for a VBA we copied that is still
not working.
The macro uses vbaGrid6.ocx ("vbAcceslator Grid Control (VB6 Version)")
Hope to answer your questions.
You mention "we need to look up for changes that are made in outlook 2010 before using vba". Even though we have working 95% of the macros, we would greatly appreciate your feedback on your comment. Maybe we have overlooked something.
Thank you very much.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Andes but still does't work.
Ramante,
Is "Andes" a typo for "Added"?
Is "Andes" a typo for "Added"?
ASKER
Sorry about that I meant: "Done it but still doesn't work"... Typo
Are you getting an error?
ASKER
Yes, "missing object".
We have identified the form in the VBA and it is a form that uses vbaGrid6.ocx ("vbAcceslator Grid Control (VB6 Version)").
We thought that maybe we needed a version for w8 and went to the site but couldn't find it.
Please note that we copied all those DLL and ran from dos prompt the "register" for the DLL and it gave us an error also (so maybe it is windows version related).
We have identified the form in the VBA and it is a form that uses vbaGrid6.ocx ("vbAcceslator Grid Control (VB6 Version)").
We thought that maybe we needed a version for w8 and went to the site but couldn't find it.
Please note that we copied all those DLL and ran from dos prompt the "register" for the DLL and it gave us an error also (so maybe it is windows version related).
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
How do we registered OCX in Windows?
Also, hot do we edit the form and re-add the control for that OCX?
Thank you.
Also, hot do we edit the form and re-add the control for that OCX?
Thank you.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We don't think we used the 64 bit version; will try.
ASKER
Sorry for the delay... we didn't find but just did....
Sorry, I don't understand your last post.
ASKER
What we meant was, where do i find the 64 bit version?
I listed the path above. If it's not there, then try searching for it.
ASKER
Oh ok... will check.
ASKER
Didn't work. Since the specific Form will be redone, will proceed to close the question.
Thanx
Thanx
ASKER
thanx
Its not advisable to use all outlook 2007 vba in outlook 2010, since some settings are changed in new version.
Thanks!
Krish.