Este site irá ter funcionalidade limitada enquanto fazemos manutenção para melhorar a sua experiência. Se um artigo não resolve o seu problema e quiser colocar uma questão, temos a nossa comunidade de apoio à espera de o ajudar em @FirefoxSupport no Twitter, /r/firefox no Reddit.

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

QuickBooks email previews in Thuderbird

  • 2 respostas
  • 3 têm este problema
  • 1 visualização
  • Última resposta por nixon3

more options

Using Thunderbird 66.0b1 as my default email with QuickBooks Enterprise 2019. About 3 weeks ago an update was installed, prior to the one today, that caused the email preview screen not to appear before sending emails out of QuickBooks. This use to provide an opportunity for me to write a comment in the email body before sending the email. Now they just get sent with no body info and the invoice or purchase order attached. My current work around is to save the PO or invoice as a PDF and then write the email in Thunderbird - which is a slow process.

Using Thunderbird 66.0b1 as my default email with QuickBooks Enterprise 2019. About 3 weeks ago an update was installed, prior to the one today, that caused the email preview screen not to appear before sending emails out of QuickBooks. This use to provide an opportunity for me to write a comment in the email body before sending the email. Now they just get sent with no body info and the invoice or purchase order attached. My current work around is to save the PO or invoice as a PDF and then write the email in Thunderbird - which is a slow process.

Todas as respostas (2)

more options

Maybe do not use beta versions of Thunderbird if you expect the most compatibility. The latest general re!ease is 60.5. The letter b in version numbers indicate beta software.

more options

Thanks for the reply. The problem first occurred with a non beta version. The beta version was installed today to hopefully fix the problem.