Group:  Microsoft Access ยป microsoft.public.access.formscoding
Thread: Can not email from form.

Geek News

Can not email from form.
"Jason" <Jason[ at ]hotmail.com> 11/29/2008 9:35:53 PM
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.


Re: Can not email from form.
"Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> 11/30/2008 2:53:37 AM
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[ at ]hotmail.com> wrote in message
news:OAzJR2mUJHA.5408[ at ]TK2MSFTNGP04.phx.gbl...
[Quoted Text]
>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.
>


Re: Can not email from form.
"Tony Toews [MVP]" <ttoews[ at ]telusplanet.net> 11/30/2008 5:13:58 AM
"Jason" <Jason[ at ]hotmail.com> wrote:

[Quoted Text]
>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.

You might be best off changing to code so it doesn't matter what
version of Outlook is installed.

Late binding means you can safely remove the reference and only have
an error when the app executes lines of code in question. Rather than
erroring out while starting up the app and not allowing the users in
the app at all. Or when hitting a mid, left or trim function call.

This also is very useful when you don't know version of the external
application will reside on the target system. Or if your organization
is in the middle of moving from one version to another.

For more information including additional text and some detailed links
see the "Late Binding in Microsoft Access" page at
http://www.granite.ab.ca/access/latebinding.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Re: Can not email from form.
"Jason" <Jason[ at ]hotmail.com> 12/2/2008 6:03:44 AM
I've already untiecked it reticked it. Doesn't say missing.
"Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
news:%23sxCcbpUJHA.6092[ at ]TK2MSFTNGP04.phx.gbl...
[Quoted Text]
> 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[ at ]hotmail.com> wrote in message
> news:OAzJR2mUJHA.5408[ at ]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.
>>
>
>


Re: Can not email from form.
"Jason" <Jason[ at ]hotmail.com> 12/2/2008 6:08:34 AM
So I would put the following code in a new module and call it from my
startup form?

Dim ref As Reference

' 0 if Late Binding
' 1 if Reference to Outlook set.
#Const ExcelRef = 0
#If ExcelRef = 0 Then ' Late binding
Dim objXL As Object
Dim objWkb As Object
Dim objSht As Object
Set objXL = CreateObject("Outlook.Application")
' Remove the Excel reference if it is present - <=======
On Error Resume Next
Set ref = References!Outlook
If Err.Number = 0 Then
References.Remove ref
ElseIf Err.Number <> 9 Then 'Subscript out of range meaning not
reference not found
MsgBox Err.Description
Exit Sub
End If
' Use your own error handling label here
On Error GoTo tagError - <=======
#Else
' a reference to MS Outlook <> Object Library must be specified
Dim objXL As Outlook.Application
'Dim objWkb As Excel.Workbook
'Dim objSht As Excel.Worksheet
Set objXL = New Oultlook.Application
#End If


"Tony Toews [MVP]" <ttoews[ at ]telusplanet.net> wrote in message
news:q684j4deh00c45eh0evj9ugnujopsg885m[ at ]4ax.com...
[Quoted Text]
> "Jason" <Jason[ at ]hotmail.com> wrote:
>
>>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.
>
> You might be best off changing to code so it doesn't matter what
> version of Outlook is installed.
>
> Late binding means you can safely remove the reference and only have
> an error when the app executes lines of code in question. Rather than
> erroring out while starting up the app and not allowing the users in
> the app at all. Or when hitting a mid, left or trim function call.
>
> This also is very useful when you don't know version of the external
> application will reside on the target system. Or if your organization
> is in the middle of moving from one version to another.
>
> For more information including additional text and some detailed links
> see the "Late Binding in Microsoft Access" page at
> http://www.granite.ab.ca/access/latebinding.htm
>
> Tony
> --
> Tony Toews, Microsoft Access MVP
> Please respond only in the newsgroups so that others can
> read the entire thread of messages.
> Microsoft Access Links, Hints, Tips & Accounting Systems at
> http://www.granite.ab.ca/accsmstr.htm
> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/


Re: Can not email from form.
"Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> 12/2/2008 3:59:06 PM
Merely unticking the checkbox, then reticking it doesn't do any good. You
need to untick the box marked MISSING: and find the correct reference in the
list.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com


"Jason" <Jason[ at ]hotmail.com> wrote in message
news:OCuFVUEVJHA.1200[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text]
> I've already untiecked it reticked it. Doesn't say missing.
> "Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
> news:%23sxCcbpUJHA.6092[ at ]TK2MSFTNGP04.phx.gbl...
>> 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[ at ]hotmail.com> wrote in message
>> news:OAzJR2mUJHA.5408[ at ]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.
>>>
>>
>>
>
>


Re: Can not email from form.
"Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> 12/2/2008 4:00:19 PM

"Jason" <Jason[ at ]hotmail.com> wrote in message
news:%23sjCrUEVJHA.1200[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text]
> So I would put the following code in a new module and call it from my
> startup form?
>
> Dim ref As Reference
>
> ' 0 if Late Binding
> ' 1 if Reference to Outlook set.
> #Const ExcelRef = 0
> #If ExcelRef = 0 Then ' Late binding
> Dim objXL As Object
> Dim objWkb As Object
> Dim objSht As Object
> Set objXL = CreateObject("Outlook.Application")
> ' Remove the Excel reference if it is present - <=======
> On Error Resume Next
> Set ref = References!Outlook
> If Err.Number = 0 Then
> References.Remove ref
> ElseIf Err.Number <> 9 Then 'Subscript out of range meaning not
> reference not found
> MsgBox Err.Description
> Exit Sub
> End If
> ' Use your own error handling label here
> On Error GoTo tagError - <=======
> #Else
> ' a reference to MS Outlook <> Object Library must be specified
> Dim objXL As Outlook.Application
> 'Dim objWkb As Excel.Workbook
> 'Dim objSht As Excel.Worksheet
> Set objXL = New Oultlook.Application
> #End If
>
>
> "Tony Toews [MVP]" <ttoews[ at ]telusplanet.net> wrote in message
> news:q684j4deh00c45eh0evj9ugnujopsg885m[ at ]4ax.com...
>> "Jason" <Jason[ at ]hotmail.com> wrote:
>>
>>>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.
>>
>> You might be best off changing to code so it doesn't matter what
>> version of Outlook is installed.
>>
>> Late binding means you can safely remove the reference and only have
>> an error when the app executes lines of code in question. Rather than
>> erroring out while starting up the app and not allowing the users in
>> the app at all. Or when hitting a mid, left or trim function call.
>>
>> This also is very useful when you don't know version of the external
>> application will reside on the target system. Or if your organization
>> is in the middle of moving from one version to another.
>>
>> For more information including additional text and some detailed links
>> see the "Late Binding in Microsoft Access" page at
>> http://www.granite.ab.ca/access/latebinding.htm
>>
>> Tony
>> --
>> Tony Toews, Microsoft Access MVP
>> Please respond only in the newsgroups so that others can
>> read the entire thread of messages.
>> Microsoft Access Links, Hints, Tips & Accounting Systems at
>> http://www.granite.ab.ca/accsmstr.htm
>> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
>
>


Re: Can not email from form.
"Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> 12/2/2008 4:05:38 PM
Sorry about the first post. I meant to close it, but sent it instead.

Late binding is a good solution for you if your are moving the database
around a lot. The lines in your code to look for are all the application
references that need changing to Object, for instance:

Dim objOutlook As Outlook.Application

would change to:

Dim objOutllook As Object
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com


"Jason" <Jason[ at ]hotmail.com> wrote in message
news:%23sjCrUEVJHA.1200[ at ]TK2MSFTNGP02.phx.gbl...
[Quoted Text]
> So I would put the following code in a new module and call it from my
> startup form?
>
> Dim ref As Reference
>
> ' 0 if Late Binding
> ' 1 if Reference to Outlook set.
> #Const ExcelRef = 0
> #If ExcelRef = 0 Then ' Late binding
> Dim objXL As Object
> Dim objWkb As Object
> Dim objSht As Object
> Set objXL = CreateObject("Outlook.Application")
> ' Remove the Excel reference if it is present - <=======
> On Error Resume Next
> Set ref = References!Outlook
> If Err.Number = 0 Then
> References.Remove ref
> ElseIf Err.Number <> 9 Then 'Subscript out of range meaning not
> reference not found
> MsgBox Err.Description
> Exit Sub
> End If
> ' Use your own error handling label here
> On Error GoTo tagError - <=======
> #Else
> ' a reference to MS Outlook <> Object Library must be specified
> Dim objXL As Outlook.Application
> 'Dim objWkb As Excel.Workbook
> 'Dim objSht As Excel.Worksheet
> Set objXL = New Oultlook.Application
> #End If
>
>
> "Tony Toews [MVP]" <ttoews[ at ]telusplanet.net> wrote in message
> news:q684j4deh00c45eh0evj9ugnujopsg885m[ at ]4ax.com...
>> "Jason" <Jason[ at ]hotmail.com> wrote:
>>
>>>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.
>>
>> You might be best off changing to code so it doesn't matter what
>> version of Outlook is installed.
>>
>> Late binding means you can safely remove the reference and only have
>> an error when the app executes lines of code in question. Rather than
>> erroring out while starting up the app and not allowing the users in
>> the app at all. Or when hitting a mid, left or trim function call.
>>
>> This also is very useful when you don't know version of the external
>> application will reside on the target system. Or if your organization
>> is in the middle of moving from one version to another.
>>
>> For more information including additional text and some detailed links
>> see the "Late Binding in Microsoft Access" page at
>> http://www.granite.ab.ca/access/latebinding.htm
>>
>> Tony
>> --
>> Tony Toews, Microsoft Access MVP
>> Please respond only in the newsgroups so that others can
>> read the entire thread of messages.
>> Microsoft Access Links, Hints, Tips & Accounting Systems at
>> http://www.granite.ab.ca/accsmstr.htm
>> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
>
>


Re: Can not email from form.
"Jason" <Jason[ at ]hotmail.com> 12/4/2008 7:34:27 AM
aS STATED - DOES NOT SAY missing
"Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
news:OoACsbJVJHA.5452[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text]
> Merely unticking the checkbox, then reticking it doesn't do any good. You
> need to untick the box marked MISSING: and find the correct reference in
> the list.
> --
> Arvin Meyer, MCP, MVP
> http://www.datastrat.com
> http://www.mvps.org/access
> http://www.accessmvp.com
>
>
> "Jason" <Jason[ at ]hotmail.com> wrote in message
> news:OCuFVUEVJHA.1200[ at ]TK2MSFTNGP02.phx.gbl...
>> I've already untiecked it reticked it. Doesn't say missing.
>> "Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
>> news:%23sxCcbpUJHA.6092[ at ]TK2MSFTNGP04.phx.gbl...
>>> 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[ at ]hotmail.com> wrote in message
>>> news:OAzJR2mUJHA.5408[ at ]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.
>>>>
>>>
>>>
>>
>>
>
>


Re: Can not email from form.
"Jason" <Jason[ at ]hotmail.com> 12/4/2008 7:35:24 AM
should it be Dim objOutLook As Object?

"Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
news:ucL8VfJVJHA.1244[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text]
> Sorry about the first post. I meant to close it, but sent it instead.
>
> Late binding is a good solution for you if your are moving the database
> around a lot. The lines in your code to look for are all the application
> references that need changing to Object, for instance:
>
> Dim objOutlook As Outlook.Application
>
> would change to:
>
> Dim objOutllook As Object
> --
> Arvin Meyer, MCP, MVP
> http://www.datastrat.com
> http://www.mvps.org/access
> http://www.accessmvp.com
>
>
> "Jason" <Jason[ at ]hotmail.com> wrote in message
> news:%23sjCrUEVJHA.1200[ at ]TK2MSFTNGP02.phx.gbl...
>> So I would put the following code in a new module and call it from my
>> startup form?
>>
>> Dim ref As Reference
>>
>> ' 0 if Late Binding
>> ' 1 if Reference to Outlook set.
>> #Const ExcelRef = 0
>> #If ExcelRef = 0 Then ' Late binding
>> Dim objXL As Object
>> Dim objWkb As Object
>> Dim objSht As Object
>> Set objXL = CreateObject("Outlook.Application")
>> ' Remove the Excel reference if it is present - <=======
>> On Error Resume Next
>> Set ref = References!Outlook
>> If Err.Number = 0 Then
>> References.Remove ref
>> ElseIf Err.Number <> 9 Then 'Subscript out of range meaning not
>> reference not found
>> MsgBox Err.Description
>> Exit Sub
>> End If
>> ' Use your own error handling label here
>> On Error GoTo tagError - <=======
>> #Else
>> ' a reference to MS Outlook <> Object Library must be specified
>> Dim objXL As Outlook.Application
>> 'Dim objWkb As Excel.Workbook
>> 'Dim objSht As Excel.Worksheet
>> Set objXL = New Oultlook.Application
>> #End If
>>
>>
>> "Tony Toews [MVP]" <ttoews[ at ]telusplanet.net> wrote in message
>> news:q684j4deh00c45eh0evj9ugnujopsg885m[ at ]4ax.com...
>>> "Jason" <Jason[ at ]hotmail.com> wrote:
>>>
>>>>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.
>>>
>>> You might be best off changing to code so it doesn't matter what
>>> version of Outlook is installed.
>>>
>>> Late binding means you can safely remove the reference and only have
>>> an error when the app executes lines of code in question. Rather than
>>> erroring out while starting up the app and not allowing the users in
>>> the app at all. Or when hitting a mid, left or trim function call.
>>>
>>> This also is very useful when you don't know version of the external
>>> application will reside on the target system. Or if your organization
>>> is in the middle of moving from one version to another.
>>>
>>> For more information including additional text and some detailed links
>>> see the "Late Binding in Microsoft Access" page at
>>> http://www.granite.ab.ca/access/latebinding.htm
>>>
>>> Tony
>>> --
>>> Tony Toews, Microsoft Access MVP
>>> Please respond only in the newsgroups so that others can
>>> read the entire thread of messages.
>>> Microsoft Access Links, Hints, Tips & Accounting Systems at
>>> http://www.granite.ab.ca/accsmstr.htm
>>> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
>>
>>
>
>


Re: Can not email from form.
"Jason" <Jason[ at ]hotmail.com> 12/4/2008 7:36:55 AM
I don't intend on copying back to that computer again - had enough of trying
to fix errors after copying back to this computer. The other computer is
really too slow for Access. But will use late binding incase I instal lan
empty copy of the database.
"Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
news:ucL8VfJVJHA.1244[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text]
> Sorry about the first post. I meant to close it, but sent it instead.
>
> Late binding is a good solution for you if your are moving the database
> around a lot. The lines in your code to look for are all the application
> references that need changing to Object, for instance:
>
> Dim objOutlook As Outlook.Application
>
> would change to:
>
> Dim objOutllook As Object
> --
> Arvin Meyer, MCP, MVP
> http://www.datastrat.com
> http://www.mvps.org/access
> http://www.accessmvp.com
>
>
> "Jason" <Jason[ at ]hotmail.com> wrote in message
> news:%23sjCrUEVJHA.1200[ at ]TK2MSFTNGP02.phx.gbl...
>> So I would put the following code in a new module and call it from my
>> startup form?
>>
>> Dim ref As Reference
>>
>> ' 0 if Late Binding
>> ' 1 if Reference to Outlook set.
>> #Const ExcelRef = 0
>> #If ExcelRef = 0 Then ' Late binding
>> Dim objXL As Object
>> Dim objWkb As Object
>> Dim objSht As Object
>> Set objXL = CreateObject("Outlook.Application")
>> ' Remove the Excel reference if it is present - <=======
>> On Error Resume Next
>> Set ref = References!Outlook
>> If Err.Number = 0 Then
>> References.Remove ref
>> ElseIf Err.Number <> 9 Then 'Subscript out of range meaning not
>> reference not found
>> MsgBox Err.Description
>> Exit Sub
>> End If
>> ' Use your own error handling label here
>> On Error GoTo tagError - <=======
>> #Else
>> ' a reference to MS Outlook <> Object Library must be specified
>> Dim objXL As Outlook.Application
>> 'Dim objWkb As Excel.Workbook
>> 'Dim objSht As Excel.Worksheet
>> Set objXL = New Oultlook.Application
>> #End If
>>
>>
>> "Tony Toews [MVP]" <ttoews[ at ]telusplanet.net> wrote in message
>> news:q684j4deh00c45eh0evj9ugnujopsg885m[ at ]4ax.com...
>>> "Jason" <Jason[ at ]hotmail.com> wrote:
>>>
>>>>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.
>>>
>>> You might be best off changing to code so it doesn't matter what
>>> version of Outlook is installed.
>>>
>>> Late binding means you can safely remove the reference and only have
>>> an error when the app executes lines of code in question. Rather than
>>> erroring out while starting up the app and not allowing the users in
>>> the app at all. Or when hitting a mid, left or trim function call.
>>>
>>> This also is very useful when you don't know version of the external
>>> application will reside on the target system. Or if your organization
>>> is in the middle of moving from one version to another.
>>>
>>> For more information including additional text and some detailed links
>>> see the "Late Binding in Microsoft Access" page at
>>> http://www.granite.ab.ca/access/latebinding.htm
>>>
>>> Tony
>>> --
>>> Tony Toews, Microsoft Access MVP
>>> Please respond only in the newsgroups so that others can
>>> read the entire thread of messages.
>>> Microsoft Access Links, Hints, Tips & Accounting Systems at
>>> http://www.granite.ab.ca/accsmstr.htm
>>> Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
>>
>>
>
>


Re: Can not email from form.
"Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> 12/4/2008 3:21:57 PM
Then the issue may be an email one. Perhaps your organization has limited
permissions for outside code sending email.

Can you simply click on a report, and use File >>> Send ? If you can't, can
you send a spreadsheet in Excel, or a Word document, using File >>> Send ?
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com


"Jason" <Jason[ at ]hotmail.com> wrote in message
news:O05ubMeVJHA.2928[ at ]TK2MSFTNGP03.phx.gbl...
[Quoted Text]
> aS STATED - DOES NOT SAY missing
> "Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
> news:OoACsbJVJHA.5452[ at ]TK2MSFTNGP05.phx.gbl...
>> Merely unticking the checkbox, then reticking it doesn't do any good. You
>> need to untick the box marked MISSING: and find the correct reference in
>> the list.
>> --
>> Arvin Meyer, MCP, MVP
>> http://www.datastrat.com
>> http://www.mvps.org/access
>> http://www.accessmvp.com
>>
>>
>> "Jason" <Jason[ at ]hotmail.com> wrote in message
>> news:OCuFVUEVJHA.1200[ at ]TK2MSFTNGP02.phx.gbl...
>>> I've already untiecked it reticked it. Doesn't say missing.
>>> "Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
>>> news:%23sxCcbpUJHA.6092[ at ]TK2MSFTNGP04.phx.gbl...
>>>> 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[ at ]hotmail.com> wrote in message
>>>> news:OAzJR2mUJHA.5408[ at ]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.
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


Re: Can not email from form.
"Jason" <Jason[ at ]hotmail.com> 12/5/2008 7:04:46 AM
worked fine until copied over from being on another computer. Just normal
setup - nothing should stop sending.

Send report:
Access can't send a message for the reason staetd in the preceding alert.
Resolve the problem, and then send the message again.

There is no alert prior to this appearing.

Word - file -send as attachment is generating an error also so looks lile
Outlook problem.

Thanks,
"Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
news:%238dbQQiVJHA.1188[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text]
> Then the issue may be an email one. Perhaps your organization has limited
> permissions for outside code sending email.
>
> Can you simply click on a report, and use File >>> Send ? If you can't,
> can you send a spreadsheet in Excel, or a Word document, using File >>>
> Send ?
> --
> Arvin Meyer, MCP, MVP
> http://www.datastrat.com
> http://www.mvps.org/access
> http://www.accessmvp.com
>
>
> "Jason" <Jason[ at ]hotmail.com> wrote in message
> news:O05ubMeVJHA.2928[ at ]TK2MSFTNGP03.phx.gbl...
>> aS STATED - DOES NOT SAY missing
>> "Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
>> news:OoACsbJVJHA.5452[ at ]TK2MSFTNGP05.phx.gbl...
>>> Merely unticking the checkbox, then reticking it doesn't do any good.
>>> You need to untick the box marked MISSING: and find the correct
>>> reference in the list.
>>> --
>>> Arvin Meyer, MCP, MVP
>>> http://www.datastrat.com
>>> http://www.mvps.org/access
>>> http://www.accessmvp.com
>>>
>>>
>>> "Jason" <Jason[ at ]hotmail.com> wrote in message
>>> news:OCuFVUEVJHA.1200[ at ]TK2MSFTNGP02.phx.gbl...
>>>> I've already untiecked it reticked it. Doesn't say missing.
>>>> "Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
>>>> news:%23sxCcbpUJHA.6092[ at ]TK2MSFTNGP04.phx.gbl...
>>>>> 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[ at ]hotmail.com> wrote in message
>>>>> news:OAzJR2mUJHA.5408[ at ]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.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>



Re: Can not email from form.
"Jason" <Jason[ at ]hotmail.com> 12/5/2008 7:18:55 AM
Don't know what happened:
Went control panel - classic view - mail - looked at settings - closed -
catagory view.

Now Access, Excel and Word can send.
"Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
news:%238dbQQiVJHA.1188[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text]
> Then the issue may be an email one. Perhaps your organization has limited
> permissions for outside code sending email.
>
> Can you simply click on a report, and use File >>> Send ? If you can't,
> can you send a spreadsheet in Excel, or a Word document, using File >>>
> Send ?
> --
> Arvin Meyer, MCP, MVP
> http://www.datastrat.com
> http://www.mvps.org/access
> http://www.accessmvp.com
>
>
> "Jason" <Jason[ at ]hotmail.com> wrote in message
> news:O05ubMeVJHA.2928[ at ]TK2MSFTNGP03.phx.gbl...
>> aS STATED - DOES NOT SAY missing
>> "Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
>> news:OoACsbJVJHA.5452[ at ]TK2MSFTNGP05.phx.gbl...
>>> Merely unticking the checkbox, then reticking it doesn't do any good.
>>> You need to untick the box marked MISSING: and find the correct
>>> reference in the list.
>>> --
>>> Arvin Meyer, MCP, MVP
>>> http://www.datastrat.com
>>> http://www.mvps.org/access
>>> http://www.accessmvp.com
>>>
>>>
>>> "Jason" <Jason[ at ]hotmail.com> wrote in message
>>> news:OCuFVUEVJHA.1200[ at ]TK2MSFTNGP02.phx.gbl...
>>>> I've already untiecked it reticked it. Doesn't say missing.
>>>> "Arvin Meyer [MVP]" <arvinm[ at ]mvps.invalid> wrote in message
>>>> news:%23sxCcbpUJHA.6092[ at ]TK2MSFTNGP04.phx.gbl...
>>>>> 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[ at ]hotmail.com> wrote in message
>>>>> news:OAzJR2mUJHA.5408[ at ]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.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>


Home | Search | Terms | Imprint Contact
Newsgroups Reader - provided by WiredBox.Net