Answers from previous concerns and questions raised during the presentation of the converted application to JSON-RPC setup.\n\n - Verify the length of StringObject Value attribute\n\t? The value attribute is indeed can only contain 2000 characters but the StringObject System Class doesn't have a limit. This will not be a problem since the only procedure that's using value attribute is the RPC-Request which may not reach 2000 characters. The RPC-result on the otherhand will definitely reach more than 2000 characters but the value attribute was never used. \n\n - Use the JsonObject to Object function to eliminate looping to get    values from the reply string\n\t? This was done successfully (please refer to the PDF file attached). This process will require a UserClass on the Client-Side to hold the data parsed from the RPC-Response.\n\n - Populate the database to test response time from the server.\n\t? The database was loaded with three thousand rows of record and there was a little delay experienced (This is on a Client-Server setup on a single laptop. Further testing are being done to check the response time from the server.\n\n - Create additional table to test nested array behaviour on JSON\n\t? As expected, there was no problem encountered on this kind of setup. the RPC-Response just created an array within the array that's already on the original setup. (Please refer to the PDF attached)\n