If anyone has the .jad file or the .cod file for this version please either post it or message me about my obtaining it from you. I know you can download it via OTA, but I am obssesive and want to always keep a copy that I can install via my desktop manager and right now I cant fine it. I already tried to obtain it from my BB via BB_Manager but it does not show up in there. Thanks.

EDIT - Unless someone knows the system file name for the BBMessenger so that I can retrieve it that way.

Just searching I went to my older version and found the names of the cod files in there, then using bb_manager and unhiding the system files I searched for those names (net_rim_bb_qm_peer.cod, net_rim_bb_qm_peer_resource_en.cod, net_rim_bb_smileys_default.cod) and copied them to my pc, created a new alx file and there it is. The only problem I have is that now the apps loader wants to downgrade, have to figure out how to have it recognize the files installed on the bb and making them match the new ones i created on my pc. When I do I will post that too.

I set up a different subfolder, in here i left the names just as they came accross. I unistalled the old which was 1.094 from OTA, and reinstalled but somehow it installed the 1.092. I then went OTA after unistalling it and reinstalled the 1.094, now when I run application loader it sees it and says it has to downgrade even though i have the new one in there, so if i add anything new to the BB it will downgrade me, so I dont know how to get around this I am in a bit worse shape than I started from since before i had 1.094 and apps loader was fine. So I have to play some more unless you have any suggestions for me to try.

Do you know if it is possible save or monitor messages from one BB to another BB using the BES server ?

4.1 BES enables auditing of Pin to Pin messages.

Here is what it does from jibi:

It synchronizes the PIN messages database on the local handheld to a CSV-formatted file on the BES server. This will contain all PIN messages - not just those sent by the user. This 'auditing' functionality is disabled by default, but can be enabled via IT Policy. It is not an encrypted file (plain-text csv). By default, it logs to the \Logs directory under the BES installation directory (as PINLog_YYYYMMDD.CSV), although you can specify another location that won't affect the other log files (an audit log root directory). Once in this location, you can place extremely restrictive permissions on the directory/share. All messages are logged in a single log file, but since its CSV, you can open in Excel or some other CSV reader and sort by Name.ID (which will contain their name and BES UID - Last, First.124) to individualize it. This is the same for SMS messages and Phone Call logs (although the latter is enabled by default; if a call was dialed from or received by an entry in a user's local address book, it will put that name/entry as the identification, along with their number).