CSPro Users Forum

They're on the page: https://www.csprousers.org/resources/. Look for "CSPro Mobile Workshop Materials."

There were a few reasons that we went with the paid encryption solution, but to your point, I encourage you to test your queries using an unencrypted .csdb file. You can do all of your testing with such files and then move to .csdbe when you're ready to collect data. At some point, I'll likely add a...

You can't because we use a different encryption scheme than SQLCipher. The only way you can open it is using a CSPro application (or if you purchase the SQLite Encryption Extension: https://www.sqlite.org/see/doc/release/www/index.wiki).

This actually works as designed but I can see how it's a bit confusing. From the helps: If this value is set, then the "Show/Hide Navigation Controls" menu option is hidden. Values: "Yes" (show) or "No" (hide) So if you set it to Yes or No, the menu option will be hidden. If you want to see the menu...

Can you send your test application where you set this in logic? If you look at the attached file, I've included an application that sets the operator ID in the _FF form preproc and it works correctly in my testing.

I think this is the same problem as this: https://www.csprousers.org/forum/viewtopic.php?f=1&t=3856 This works correctly on Windows but not on Android. It's fixed for CSPro 7.4 but for now, you can get correct behavior if you save the PFF using a filename that starts with different characters than t...

Just as an update, we've fixed this problem for CSPro 7.4. Thanks for reporting it.

1) This is the operator ID that the user can enter (https://www.csprousers.org/help/CSPro/change_data_entry_options.html). If you want to set it via logic, you can use the setoperatorid function. 2) This is a UNIX time value, which contains both the date and time. You can work with times in CSPro lo...

Hello Leo, CSPro 7.4 has several things that will help you. Firstly, the Index Data tool now works with .csdb files. Secondly, you can use the set access function in a batch application to only process your duplicate cases. If you can wait, in a few days we should be putting out the beta of this ver...

This is a bit of a hack, but if you have one final field (even if it's just a control field) on the form, you could prevent moving backwards with code like this: PROC GLOBAL numeric CanLeaveForm; PROC MY_FORM onfocus CanLeaveForm = false ; killfocus if not CanLeaveForm then move FIRST_FIELD_ON_FORM ...