Access 2007 runtime error 287 application-defined...

  • Thread starter Thread starter Jim
  • Start date Start date
J

Jim

I have a simple access database used to track members, print lists and send
email, developed using Office 2007 on Windows Vista. When I click the email
button it pops up a form to prompt for selection criteria then loads an
outlook email. Works fine. But when I install the runtime on a Windows XP
everything works fine except the email. After the selection form pops up and
I click continue, I get the message 'Runtime error 287 application-defined or
object-defined error.

Does anyone have any ideas?

FYI. I tested the runtime on Windows Vista and it works. The XP is Windows
XP Professional SP 3.
 
Jim said:
I have a simple access database used to track members, print lists and send
email, developed using Office 2007 on Windows Vista. When I click the email
button it pops up a form to prompt for selection criteria then loads an
outlook email. Works fine. But when I install the runtime on a Windows XP
everything works fine except the email. After the selection form pops up and
I click continue, I get the message 'Runtime error 287 application-defined or
object-defined error.
Click to expand...

Do you have a reference to Outlook set? Is that PCs version of
Windows Outlook different than your version?

If so use Late Binding

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/
 
--
JBM


Tony Toews said:
Do you have a reference to Outlook set? Is that PCs version of
Windows Outlook different than your version?

If so use Late Binding

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/
Click to expand...

Both systems have Office 2007, but this could be used on systems that do not
so I'll code for late binding and see if that takes care of this issue also.

I'll post my results when finished.
 
I figured late binding was a long shot but still worth the effort, however it
doesn't solve my original issue.

Both systems have Office 2007 installed and Outlook works fine on both
systems. The only variation I can see is that the project was developed on a
system with Vista.
 
That didn't solve my issue, it was still worth the effort as I will be
needing it in the future, but first I have to figure out why it doesn't work
on Vista.

Both systems are running Office 2007 so teh only difference is the OS.
 
Are you sure the application isn't looking at Windows Mail because Outlook
does not come on a Vista machine. I would check the refrences.
 
You're right, but I installed Office 2007 and included Outlook primarily for
development purposes. At this time I'm not using this one for me email
though it is connected and can send/receive email.

I just discovered another clue.
On the Vista system the app works regardless whether Outlook is currently
open, but on the XP system I only get the error if Outlook is not open. If
Outlook is already open than the application works just fine.
 
I would still check the references because something is off. The reference
for MS Outlook 2007 is bound to be different then the one for MS Outlook
2003.

If outlook has to be open on the XP machine sounds like a coding issue.
What does the error mesage say?
 
Back
Top