Q:

String Array in SharedPreferences

I need to work with a persistent String Array (n Rows, 1 column).
* On first running the app, the String Array needs to be created empty.
* On subsequent app executions the Array will be populated from a File and the contents need to be available throughout the rest of the app.
* As the app is executed, the Array needs to be able to 'grow' in row count
* As the app is executed, the Array rows need to be able to grow in length
* The user will have the option to Clear the Array of previous entries.
* At the end, the String Array contents will be written back to a File.
I find a lot of references to Putting and Getting from an existing SharedPreferences String[] but, in the newness of my Android development, I am struggling with how to proceed.
EDIT Follows...
The data itself suggests using an Array 
Example: 
MAIN ST.    F55     63      KY08:57 12142015--------KY11:24 12142015345TMH  KY13:57 12142015
MAIN ST.    F56     WYE123  IN08:57 12142015--------KY11:24 12142015--------KY13:57 12142015
1ST ST.     F57     --------KY08:57 12142015--------KY11:24 12142015789FPF  KY13:57 12142015
1ST ST.     F58     456FPF  KY08:57 12142015998FPF  KY11:24 12142015--------KY13:57 12142015
1ST ST.     F59     789TTM  KY08:57 12142015--------KY11:24 121420151234DG  KY13:57 12142015

I first need to have this data in a File
Then in one GUI I check for the existence of the file.
If one exists, fine
If none exists, I create one.
Then, in subsequent GUI's, I must check for the existence of parameters
If they do not already exist, add them to the existing data lines.
If they already exist, notify the user
And so on and on.
Then when all of the current 'pass' data has been collected via multiple, separate GUI's, I have to write out the whole data-set into the file.
My reason for thinking that I need a SharedPreference approach is the need to find and check data from GUI to GUI as the user progresses through the app. 
If that 'belief' is wrong, I am open to better approach suggestions. 
EDIT 2 follows....
On further study of web references, I am beginning to think that perhaps the best approach for this data and how the data needs to change might be to use a SQLite approach.   Any ideas about this?
Any assistance/suggestions you might have would be greatly appreciated.

A:

OK, based on the data, how it needs to be manipulated and the pros and cons of using a SharedPreferences approach, I have decided to go with a SQLite approach.
With that approach I should be able to readily check:
* if the necessary table exists (if not create it)
* if the necessary Field1 + Field2 exists  (if not create a new record)
* and I will be able to modify the record's Field3 contents as needed  
Then when the user's actions are complete I can convert the SQLite table 'records' into strings and write them out as a File and then either DROP or PURGE the associated SQLite table (until needed next time).
I sincerely appreciate all of your suggestions.
Thank you.

