Can you post your application or send it to us at cspro@lists.census.gov? Also please send steps to reproduce the problem and let us know whether you are using Android for client and server or if it is Windows and Android.
Thank you for the very excellent test application. I was able to easily reproduce the problem. This is a bug that occurs because the server application opens the data file as read-only. We will fix it in the next release.
In the meantime there is a workaround. If you add a writecase statement somewhere in the server application this will force CSPro to open the data file as read-write instead of read-only. So if you add a function like this one in your PROC GLOBAL it will fix the problem. You don't need to actually call the function. Just the fact that it is there is sufficient.
PROC GLOBAL
function makeCSProOpenExternalDictAsWriteable()
writecase(EXTDATAFILE_DICT);
end;
Note that you may need to delete the existing data file on the server in receivedData when you run this the first time. This is because the earlier failure leaves that data file in a corrupt state.
I tried with new version of CSPro (CSPro 7.6.0 Release Date 2021-03-31) and got errors with the same attached (CSPBT75.zip / March 17th, 2021) program.
Errors are attached (SyncTest2.pdf), please guide me
This time I used different two tablets to test the synchronization. As you suggested PEN files built with CSPRO 76. I regenerated pff files and the database using CSPro 76. It is strange, same happening. (Error in SyncTest3.pdf)
I retested the issue and I was able to reproduce the issue. We thought this issue was fixed, but let us take a bit more time to take a look at it. As Josh mentioned previously, your workaround is to add the writecase. Thanks for reporting this again.
aaronw wrote: ↑April 16th, 2021, 4:43 pm
I retested the issue and I was able to reproduce the issue. We thought this issue was fixed, but let us take a bit more time to take a look at it. As Josh mentioned previously, your workaround is to add the writecase. Thanks for reporting this again.