Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
07-17-2008 01:11 PM
Quote from the previous forum:
When i push an upgrade of my midlet to the device it clears the Record store
Whats the reson for that?can it be fixed?
If an application is recompiled, it will not be able to access its existing RMS data stores. Because of the recompilation, the application is not considered to be the same as the previous version and will not be allowed access to the RMS data stores on the simulator. This feature is part of the persistent data access security architecture.
07-17-2008 07:14 PM
10-08-2008 02:54 PM
Update to my previous post:
The RMS RecordStore should remain when an application is upgraded.
A BlackBerry handheld considers an update to be when you download an application which has the same MIDlet-Name and MIDlet-Vendor attributes and a different MIDlet-Version attribute of a MIDlet already on the device.