No coding was done in Outlook. This is what baffles me. The custom
Outlook form was developed in 2K2. No changes were done to any coding
when I brought it into the 2K3 environment. I opened the custom form
in Outlook 2K3 to check for any variance. Then I ran the import
utility in Access, but then I stopped it in Outlook, when the program
security window popped up. I did some minor changes to the Access
forms (no coding, just looks and links to reports and queries), but
again no module changes. When I brought it back to the 2K2
environment, it was asking for the Outlook 11.0 Object Library in
Access. I finally found it in the Office 2K3 CD, after flipping back
and forth between Office 2K3 and Office 2K2 in the server (in other
words, installing 2K3, removing it and re-installing 2K2, yeah, I
know...not a good thing to do). I installed the library and then
everything was working fine again in the 2K2 environment. The next
day "something" decided not to work. I know what MAPI does, as I am
primarily a Network Tech. If the MAPI problem was the issue, it
should have shown up when I changed over from Outlook Obj Lib 10.0 to
11.0. It didn't. I tested it out on a machine that did not have
Exchange on it, that was a standalone XP box with Off 2K2 to confirm
it was not a corruption of the MAPI dlls on the server when I upgraded
to 2K3 and then returned to 2K2. It runs fine on my XP box with Off
2K3 on it. I am getting to the point where I will need to go back to
an older version of the DB and recreate it. This would mean a couple
of long evenings worth of work, but this code was definitely all done
in 2K2, before it was brought into the 2K3 environment at all. Maybe
recreate the Outlook form? I am including it as an attachment, maybe
someone can see if there is something there? The thing is no coding
is done there. All the custom fields were already done in 2K2.

Thanks again for hate help so far, and for any new help offered.

Oliver

On Sat, 31 Mar 2007 13:55:20 -0400, "Ken Slovak - [MVP - Outlook]"
wrote:

Import what?

This code is in Outlook VBA code?

The MAPI libraries are installed by Outlook, Simple MAPI can be installed by
Outlook Express, Eudora installs a version of MAPI, the term MAPI is rather
general. In this case it's Outlook MAPI that has to be dealt with. It's
always a good idea to make sure that Outlook is the default mail handler and
that it's installed correctly. So open IE, on Programs tab make sure Outlook
is the mail handler. Then run a Detect and Repair on your Office
installation.

Outlook MAPI is very version specific. So if you are developing in Access
2002 you will want to run an Office 2002 environment. If you develop on 2003
you must make sure you aren't using any methods, properties or events that
aren't in the earlier version. After you port back to the older environment
you must also make sure the project references are set correctly.

Never, ever run Outlook 2003 on an Exchange server. Do not do it. Outlook
2007 is OK for that. Earlier versions will corrupt the MAPI on the server
unless you really know what you're doing.

Instantiating a MAPI session failing like that has nothing to do with
pointing towards a certain version of MAPI. The high level connection you
are using with MAPI just depends on what version is registered and the
default MAPI handler. You aren't using a LoadDLL type thing and trying to
execute Extended MAPI functions like HrGetOneProp directly.

I've taken Outlook and Access applications back and forth among versions and
the best practice is really to develop in the earliest environment you need
to support. I use VM's with every Outlook/Office environment I need to
support so I can develop on any of them as needed. Usually I program
(addins) on an Office 2003 machine and compile on an Office 2000 VM. I'm
always adjusting project references and such, but you do need that earlier
environment available to be able to do that.

If you move Outlook 2002 code to an Outlook 2003 environment the references
to Outlook are replaced with references to Outlook 2003. If you move it back
to Office 2002 you must re-set the references back to Outlook 2002. That's
all it takes. Otherwise the CLSID references to Outlook reference a version
not available on the Office 2002 box. That applies also to any Outlook code
in Access, where unless you are late-binding you are referencing the version
of Outlook on the dev box.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"The Facilitator" wrote in message
...
No coding was done in Outlook. This is what baffles me. The custom
Outlook form was developed in 2K2. No changes were done to any coding
when I brought it into the 2K3 environment. I opened the custom form
in Outlook 2K3 to check for any variance. Then I ran the import
utility in Access, but then I stopped it in Outlook, when the program
security window popped up. I did some minor changes to the Access
forms (no coding, just looks and links to reports and queries), but
again no module changes. When I brought it back to the 2K2
environment, it was asking for the Outlook 11.0 Object Library in
Access. I finally found it in the Office 2K3 CD, after flipping back
and forth between Office 2K3 and Office 2K2 in the server (in other
words, installing 2K3, removing it and re-installing 2K2, yeah, I
know...not a good thing to do). I installed the library and then
everything was working fine again in the 2K2 environment. The next
day "something" decided not to work. I know what MAPI does, as I am
primarily a Network Tech. If the MAPI problem was the issue, it
should have shown up when I changed over from Outlook Obj Lib 10.0 to
11.0. It didn't. I tested it out on a machine that did not have
Exchange on it, that was a standalone XP box with Off 2K2 to confirm
it was not a corruption of the MAPI dlls on the server when I upgraded
to 2K3 and then returned to 2K2. It runs fine on my XP box with Off
2K3 on it. I am getting to the point where I will need to go back to
an older version of the DB and recreate it. This would mean a couple
of long evenings worth of work, but this code was definitely all done
in 2K2, before it was brought into the 2K3 environment at all. Maybe
recreate the Outlook form? I am including it as an attachment, maybe
someone can see if there is something there? The thing is no coding
is done there. All the custom fields were already done in 2K2.

Thanks again for hate help so far, and for any new help offered.

Oliver

The code is Access 2002 VBA importing task information from Outlook
2002, both standard and custom fields.

Thank you for the insight. I was able to clear it up by your (and
others suggestions) to clean up the library files in Access as they
pointed to some 2003 OLBs. Once I did that, I had everything working
on the test machine I was working on.
I now have a related problem. I was able to get the coding to work
flawlessly on the machine I set up, but when I went to install on the
client's workstation, I got the same Error loading DLL. So I went
into the code and sure enough it was stopped at the NameSpace("MAPI"),
yet again. So I went searching on the client's machine and found that
they have most of Office in 2002, but have Visio viewer and/or Project
2003 on the machines I will be copying to. The physical setup is also
different as the DB is on a mapped Network drive and they are running
it from a shortcut. I looked through the references and all was
working fine, nothing was missing.
Because they have the Visio viewer to look at email attachments, is
this affecting things? If not, what is the problem?

Again, thanks for all the help both received already and that I hope
to receive in the future.

O

On Sat, 31 Mar 2007 13:55:20 -0400, "Ken Slovak - [MVP - Outlook]"
wrote:

Import what?

This code is in Outlook VBA code?

The MAPI libraries are installed by Outlook, Simple MAPI can be installed by
Outlook Express, Eudora installs a version of MAPI, the term MAPI is rather
general. In this case it's Outlook MAPI that has to be dealt with. It's
always a good idea to make sure that Outlook is the default mail handler and
that it's installed correctly. So open IE, on Programs tab make sure Outlook
is the mail handler. Then run a Detect and Repair on your Office
installation.

Outlook MAPI is very version specific. So if you are developing in Access
2002 you will want to run an Office 2002 environment. If you develop on 2003
you must make sure you aren't using any methods, properties or events that
aren't in the earlier version. After you port back to the older environment
you must also make sure the project references are set correctly.

Never, ever run Outlook 2003 on an Exchange server. Do not do it. Outlook
2007 is OK for that. Earlier versions will corrupt the MAPI on the server
unless you really know what you're doing.

Instantiating a MAPI session failing like that has nothing to do with
pointing towards a certain version of MAPI. The high level connection you
are using with MAPI just depends on what version is registered and the
default MAPI handler. You aren't using a LoadDLL type thing and trying to
execute Extended MAPI functions like HrGetOneProp directly.

I've taken Outlook and Access applications back and forth among versions and
the best practice is really to develop in the earliest environment you need
to support. I use VM's with every Outlook/Office environment I need to
support so I can develop on any of them as needed. Usually I program
(addins) on an Office 2003 machine and compile on an Office 2000 VM. I'm
always adjusting project references and such, but you do need that earlier
environment available to be able to do that.

Visio and Project should not affect things.

I have no idea what the problem is other than an extension of the same
problems as before. I move code from Outlook 2000 to 2007 to all versions in
between without problems but I always make sure of what's being referenced
and what methods and properties I'm calling to only use those used in the
earliest version I plan to support.

The best approach however for most people is to develop on the same version
and the customer will use. That guarantees that no incompatibilities are
there.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"The Facilitator" wrote in message
...
The code is Access 2002 VBA importing task information from Outlook
2002, both standard and custom fields.

Thank you for the insight. I was able to clear it up by your (and
others suggestions) to clean up the library files in Access as they
pointed to some 2003 OLBs. Once I did that, I had everything working
on the test machine I was working on.
I now have a related problem. I was able to get the coding to work
flawlessly on the machine I set up, but when I went to install on the
client's workstation, I got the same Error loading DLL. So I went
into the code and sure enough it was stopped at the NameSpace("MAPI"),
yet again. So I went searching on the client's machine and found that
they have most of Office in 2002, but have Visio viewer and/or Project
2003 on the machines I will be copying to. The physical setup is also
different as the DB is on a mapped Network drive and they are running
it from a shortcut. I looked through the references and all was
working fine, nothing was missing.
Because they have the Visio viewer to look at email attachments, is
this affecting things? If not, what is the problem?

Again, thanks for all the help both received already and that I hope
to receive in the future.

O

That is what I did with the test environment. The client is on a
Windows 2000 machine using office 2002 and using Exchange 2003. I
emulated that and have no issues on my system or any other system I
try, 2002, 2003, XP, etc. So the only thing to do is check with their
IT department to know exactly what changes may have been set up on
their systems and see where the differences are?


On Fri, 13 Apr 2007 09:17:56 -0400, "Ken Slovak - [MVP - Outlook]"
wrote:

Visio and Project should not affect things.

I have no idea what the problem is other than an extension of the same
problems as before. I move code from Outlook 2000 to 2007 to all versions in
between without problems but I always make sure of what's being referenced
and what methods and properties I'm calling to only use those used in the
earliest version I plan to support.

The best approach however for most people is to develop on the same version
and the customer will use. That guarantees that no incompatibilities are
there.

Seeing what the differences are is the only way I think.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"The Facilitator" wrote in message
...
That is what I did with the test environment. The client is on a
Windows 2000 machine using office 2002 and using Exchange 2003. I
emulated that and have no issues on my system or any other system I
try, 2002, 2003, XP, etc. So the only thing to do is check with their
IT department to know exactly what changes may have been set up on
their systems and see where the differences are?