Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Web and WebWorks Development


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.


Reply
axg
Contributor
Posts: 10
Registered: ‎04-20-2012
My Device: PlayBook
My Carrier: AT&T

Re: SQLite DB encryption

Thanks for the inputs everyone. I'll keep them in mind going forward.

 

Tim, thanks for clearing this. Having this information documented somewhere would definitely help.

Developer
Posts: 1,230
Registered: ‎03-20-2011
My Device: Playbook, Z10 LE, Dev Alpha B, 2x Dev Alpha C
My Carrier: 3, Orange, Vodafone

Re: SQLite DB encryption

[ Edited ]

Documentation is easy

 

Give  badly written instructions and see what happens

 

I used to do this in the mid 90s as part of my QC

 

Sticking some guy/ess was invaluable for Murdocks empire (I quit)

 

We ended up with flawless instructions merely by repetition of using the exact wording on the dox

 

We had over 50 staff at the time and every new one got the rather unpleasurable task on day one of going thru a less than fun meeting with me - Sit Down - Read Paper - Do As It Says - Then wipe machine and do it again (a very boring workday)

 

One part of the instructions was - if it goes wrong, tell me what and why

 

Many of those people are good friends today

 

Simply put documentation requires idiots and software so us cleverer ppl can fix the dox




Click the like button if you find my posts useful!