>>>>> I've already untiecked it reticked it. Doesn't say missing.
>>>>>> My believe that you are correct, it is because of the copying. Open
>>>>>> any code window and check the menu item:
>>>>>>
>>>>>> Tools >>> References
>>>>>>
>>>>>> then look at the one for Microsoft Outlook. It is most likely marked
>>>>>> as missing. Uncheck it and find the reference to the correct version
>>>>>> of Outlook on that particular computer. You may need to do that each
>>>>>> time you move the database. Broken references will cause many other
>>>>>> issues as well and must be fixed for the database to run. Check out
>>>>>> Doug Steele's references page:
>>>>>>
>>>>>>
http://www.accessmvp.com/DJSteele/AccessReferenceErrors.html
>>>>>>
>>>>>> --
>>>>>> Arvin Meyer, MCP, MVP
>>>>>>
http://www.datastrat.com
>>>>>>
http://www.mvps.org/access
>>>>>>
http://www.accessmvp.com
>>>>>>
>>>>>>
>>>>>> "Jason" <Jason@hotmail.com> wrote in message
>>>>>> news:OAzJR2mUJHA.5408@TK2MSFTNGP04.phx.gbl...
>>>>>>>I get:
>>>>>>> Run-time error '2292':
>>>>>>>
>>>>>>> can't send message for the reason ated in the previous alert.
>>>>>>> Resolve the problem, and then send the message again.
>>>>>>>
>>>>>>> Microsoft Outlook 11.0 object library is ticked.
>>>>>>> There is no previous stated alert.
>>>>>>> I suspect this is caused by copying this database on to a computer
>>>>>>> with Office XP/2002 and back to a computer with Office 2003.
>>>>>>> Using Access 97.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> J.
>>>>>>>
>>>>>>
>>>>>>