I don't need toString values, I already have string values. The MySQL values come from DateTime fields which are given as strings as well as HTML forms which are also strings. You are thinking of Unix Timestamps/Epoch time or Timestamps in MySQL which I don't use. They usually start at a certain date- For Unix it is 1970. If 32bit then you run into limits. Android/Java uses 64bit, so I actually use them in my Android Databases. These string values read from MySQL, web, and even Android dialogs/fields need parsed and displayed. When storing, parsing, and displaying I keep date and time together as one field.
There have been some discussions in the past about processing this with DateTime in B4A. Many get confused by the naming and don't realize you can make the two formats whatever you want. You can make TimeFormat be a date string and when you Parse Time it really parses a date. Or you can make one of the Format strings be date and time and process it with one function. In a few threads I clarified this for users before and mentioned the naming was confusing. Many users need to process both and tried just concatenating on their own a lot and got it wrong with missing DST shifts and such from splitting time away from their date. A function was needed to process both, but I think Erel misunderstood the request and in 2.50 he made a new function to process both, but it does it by still keeping two strings and splitting time from date. It made the parsing easier by skipping a step and doing it in one function, but it is still doing it the same as before. It needs to process the parse with one string.