Search found 1790 matches
- July 15th, 2014, 11:01 am
- Forum: Entry
- Topic: Query in cspro
- Replies: 6
- Views: 6964
Re: Query in cspro
You can make your ID field both protected and persistent, and then write code like this: PROC ID preproc if demode () = add then if visualvalue (ID) = notappl then // this is the first case in the data file ID = 1 ; else // this is the second, third, etc. case in the data file ID = visualvalue (ID) ...
- July 15th, 2014, 10:04 am
- Forum: Entry
- Topic: Case ids '%s' duplicate an existing case!
- Replies: 2
- Views: 3182
Re: Case ids '%s' duplicate an existing case!
Are you automatically assigning the IDs to the field (using logic, instead of keying in the value)? For example, if you had logic like this, and ID was a protected field: PROC ID preproc ID = 5 ; That would work for the first case, but for every other case you would get an error about duplicate case...
- July 15th, 2014, 9:59 am
- Forum: Feature Requests
- Topic: Roster feature on Android orTwo or more items in one screen
- Replies: 2
- Views: 5278
Re: Roster feature on Android orTwo or more items in one sc
The first version of the Android application will only show one question per screen. In the next round, we plan to implement rosters and multiple fields per screen. If you are creative, you may be able to figure out ways to ask your questions so that the one-question-per-screen limitation is not too...
- July 14th, 2014, 2:59 pm
- Forum: Entry
- Topic: Autocomplete in Csentry
- Replies: 4
- Views: 5770
Re: Autocomplete in Csentry
Right now there is no convenient option for doing this. Perhaps you could use the selcase function to simulate the behavior of an autocomplete field, though that would force the user to type part of the response and press Enter without seeing if the response is valid. PROC AUTOCOMPLETE_FIELD if selc...
- July 14th, 2014, 12:53 pm
- Forum: Editing
- Topic: Problems exporting a data set
- Replies: 1
- Views: 4103
Re: Problems exporting a data set
What version of CSPro are you using?
If you want, you can send me your dictionary and I can take a look at the problem. Send it to csprousers@gmail.com.
If you want, you can send me your dictionary and I can take a look at the problem. Send it to csprousers@gmail.com.
- July 14th, 2014, 12:48 pm
- Forum: Entry
- Topic: Query in cspro
- Replies: 6
- Views: 6964
Re: Query in cspro
Is ITEMNAME a singly- or multiply-occurring item? I still don't understand what you are trying to do? Do you want ITEMNAME to be 1 for the first case in your data file, 2 for the second case, 3 for the third case, and so on? If so, this code will never work, because ITEMNAME will always start out as...
- July 14th, 2014, 12:40 pm
- Forum: Entry
- Topic: pff file in android cspro application
- Replies: 6
- Views: 6371
Re: pff file in android cspro application
When you run your data entry application on Windows, a .pff file will automatically be created by CSEntry, the Windows-based data entry tool. You copy this file, along with the .pen file, to your Android device and then you will be able to run your data entry application on your mobile device. See m...
- July 14th, 2014, 12:30 pm
- Forum: Entry
- Topic: Batch file in android
- Replies: 2
- Views: 2973
Re: Batch file in android
Can you incorporate CSPro logic like this?
filecopy("file.dat",maketext("file%08d%06d.dat",sysdate("YYYYMMDD"),systime()));
You could specify the path of the storage dictionary in the maketext function, if needed.- July 10th, 2014, 8:08 pm
- Forum: Entry
- Topic: Query in cspro
- Replies: 6
- Views: 6964
Re: Query in cspro
1) All values are reset every time you start adding a new case, so ITEMNAME will always be notappl. It will no longer be notappl after you have entered a value into the field. What example are you trying to do with this code? 2) I was able to recreate your behavior with the sequential bug and I am n...
- July 10th, 2014, 7:20 pm
- Forum: Entry
- Topic: Long error messages in Android version
- Replies: 4
- Views: 4348
Re: Long error messages in Android version
Ah okay, I see what the problem is. You were using an errmsg with buttons, whereas in my test I didn't add any buttons. They message text gets displayed in a different place when you use buttons, and you're right that it was truncated after two lines, which is the default Android behavior for these ...