Expand my Community achievements bar.

SOLVED

mailDoc method fails in 64 bit Office / Windows environment.

Avatar

Level 2

Hi fellow LiveCycle devs...

I've created a form in Livecycle 8.05.2073 which utilises myDoc.mailDoc method. It's been working great in production for 9 months, until... it's been used in a 64 bit environment (64 bit Outlook on 64 bit Windows 7). It fails with the following popup from 'Microsoft Office Outlook':

"Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Outlook and set it as the default mail client."

Outlook is the deafult mail client and the default handler for MAPI requests on the 64 bit workstation.

MSDN suggest that 32 bit processes can't call 64 bit processes. ref: http://msdn.microsoft.com/en-us/library/dd941355(office.14).aspx

Does anyone know of LiveCycle support for 64 bit environments?

Kind regards,

Dave.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

There is no support for the 64 bit mail client at this time.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

There is no support for the 64 bit mail client at this time.

Paul

Avatar

Level 1

When will Aobe Acrobat support Office 2010 64 bit and Windows 7 64 bit?

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----