Power Broker Website

Notes from Program Team:

Friday, October 16, 2009

The change I made will only impact NEW templates created after applying the latest update.

The New template must be marked as “F” for French for accents to translate correctly. This causes Power Broker to use a different base template that looks to import the data from a .csv file ( comma delimited ) and not for the foxpro table. The .csv would be creatd in the userid folder along with the .doc and .dbf file.

With the experiments I did I found that the French accents would translate correctly where the foxpro template table has 128 fields or less. That is why customer templates worked since they have 97 fields. By taking the extra step to copy the information contained in the template.dbf file into a .csv file and having the template know to retrieve the information from the .csv file it appears to have resolved the problem.

This causes Power Broker to use a different base template that looks to import the data from a .csv file ( comma delimited ) and not for the foxpro table. The .csv would be creatd in the userid folder along with the .doc and .dbf file.

May 1, 2009

Suite à une suggestion faite par un technicien en informatique au Québec, un tout petit changement dans un de vos programmes informatiques permet d’éliminer le problème des caractères erronés lors de l’intégration Microsoft Word.

Si vous utilisez l’intégration Microsoft Word et que vos lettres n’affichent pas les accents correctement, veuillez suivre les étapes suivantes :

Dans le panneau de configuration, ouvrez le BDE Administrator, sous l’onglet CONFIGURATION, cliquez sur DRIVERS, ensuite NATIVE, ensuite ouvrez DBASE.

Changez le « Langdriver » à ‘ascii’ ANSI.

Sortez et revenez dans Power Broker et testez en faisant une lettre avec l’intégration Word.

Si vous avez des questions ou des inquiétudes concernant ces changements ou que vous avez besoin d’assistance, n’hésitez pas à contacter votre soutien informatique local.

Merci

Thanks to a suggestion made by a local technical support person in Quebec, a computer setting change has eliminated the invalid character being displayed with Microsoft Word Integration.

Should you use Microsoft Word Integration, and your letters do not display the proper French accents, please follow these included steps and then test with one of your word integration letters.

In the control Panel, under BDE Administrator; in the Configuration tab, under Drivers, Native, DBASE:

Change the LANGDRIVER from dBASE ENU cp437 to ‘ascii’ ANSI

Should you have any questions or concerns with these changes, please contact your local technical support person for assistance.

Thank you.



French Accents
Notes from Program Team: Friday, October 16, 2009 The change I made will only impact NEW templates created after applying the latest update. The New template must be marked as “F” for French for accents to translate correctly. This causes Power Broker to use a different base template that looks to import the data from a .csv file ( comma delimited ) and not for the foxpro table. The .csv would be creatd in the userid folder along with the .doc and .dbf file. With the experiments I did I found that the French accents would translate correctly where the foxpro template table has 128 fields or less. That is why customer templates worked since they have 97 fields. By taking the extra step to copy the information contained in the template.dbf file into a .csv file and having the template know to retrieve the information from the .csv file it appears to have resolved the problem. This causes Power Broker to use a different base template that looks to import the data from a .csv file ( comma delimited ) and not for the foxpro table. The .csv would be creatd in the userid folder along with the .doc and .dbf file. May 1, 2009 Suite à une suggestion faite par un technicien en informatique au Québec, un tout petit changement dans un de vos programmes informatiques permet d’éliminer le problème des caractères erronés lors de l’intégration Microsoft Word. Si vous utilisez l’intégration Microsoft Word et que vos lettres n’affichent pas les accents correctement, veuillez suivre les étapes suivantes : Dans le panneau de configuration, ouvrez le BDE Administrator, sous l’onglet CONFIGURATION, cliquez sur DRIVERS, ensuite NATIVE, ensuite ouvrez DBASE. Changez le « Langdriver » à ‘ascii’ ANSI. Sortez et revenez dans Power Broker et testez en faisant une lettre avec l’intégration Word. Si vous avez des questions ou des inquiétudes concernant ces changements ou que vous avez besoin d’assistance, n’hésitez pas à contacter votre soutien informatique local. Merci Thanks to a suggestion made by a local technical support person in Quebec, a computer setting change has eliminated the invalid character being displayed with Microsoft Word Integration. Should you use Microsoft Word Integration, and your letters do not display the proper French accents, please follow these included steps and then test with one of your word integration letters. In the control Panel, under BDE Administrator; in the Configuration tab, under Drivers, Native, DBASE: Change the LANGDRIVER from dBASE ENU cp437 to ‘ascii’ ANSI Should you have any questions or concerns with these changes, please contact your local technical support person for assistance. Thank you.