nxbp
asked on
Lotus Notes and RIM Desktop Manager compatibility problem ?
Hi,
I need help with Lotus Notes 6.5.2 and RIM Desktop Manager 4.0.1 for Blackberry handheld terminal. My problem is : I cannot use these sofware at the same time because they use the same configuration file « notes.ini » and they’re changing the value of the « Location » parameter :
· Lotus Notes writes « R,seau » as the default value ("network" in French, with a DOS code page)
· The Destop Manager (DM) writes « Réseau » as the default value (same word, but with a Windows code page)
· Lotus Notes and the Desktop Manager seems to use two different character sets.
After first use of the DM, when Lotus Notes read the « notes.ini » file, it cannot find the correct value (« r,seau ») and ask the user for the default location.
If I change the DM value by the Notes value, when I start the DM, it asks me for the default location…
Could anyone help me please ?
I need help with Lotus Notes 6.5.2 and RIM Desktop Manager 4.0.1 for Blackberry handheld terminal. My problem is : I cannot use these sofware at the same time because they use the same configuration file « notes.ini » and they’re changing the value of the « Location » parameter :
· Lotus Notes writes « R,seau » as the default value ("network" in French, with a DOS code page)
· The Destop Manager (DM) writes « Réseau » as the default value (same word, but with a Windows code page)
· Lotus Notes and the Desktop Manager seems to use two different character sets.
After first use of the DM, when Lotus Notes read the « notes.ini » file, it cannot find the correct value (« r,seau ») and ask the user for the default location.
If I change the DM value by the Notes value, when I start the DM, it asks me for the default location…
Could anyone help me please ?
Can you change the name of you location to Network, instead of Réseau? Or just remove the accent? By the way, where is that word used?? I might be making wrong assumptions again... :$
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks to all. The bug is solved with the latest version of the software
Well, I did mention that 4.1 was out, which is the latest version.