Maximum of questions ODK can support

Development
1
  1. How many question questions ODK collect can support?

2)I want to match two fields 1)User Entered 2)Calculated. Until they both
do not match, user should not move ahead in form.

Regards
techbyte

2

  1. Depends on how many languages, how much relevancy, and how much RAM
    is in your device. I've seen usable surveys with a few thousand
    prompts.

  2. Put a constraint that compares the two.

Use a separate prompt later in the form

Compare when user is entering data

··· On Thu, Dec 6, 2012 at 7:45 AM, techbyte wrote: > 1) How many question questions ODK collect can support? > > 2)I want to match two fields 1)User Entered 2)Calculated. Until they both > do not match, user should not move ahead in form. > > Regards > techbyte >
3

Scenario is like this,

Step 1: Prompt > Enter Retail Sale:

Step 2: Prompt > Enter Retail Sale for Segment 1:
Step 3: Prompt > Enter Retail Sale for Segment 2:
Step 4: Prompt > Enter Retail Sale for Segment 3:

Step 5: Total Segment Wise Sale = Retail Sale for Segment 1 +Retail Sale
for Segment 2 + Retail Sale for Segment 3

Check Total Segment Wise Sale == Retail Sale, if not matches show warning
and do not move ahead.

How do i show calculated field on screen.

Thanks

··· On Thursday, December 6, 2012 9:27:50 PM UTC+5:30, Yaw Anokwa wrote: > > 1. Depends on how many languages, how much relevancy, and how much RAM > is in your device. I've seen usable surveys with a few thousand > prompts. > > 2. Put a constraint that compares the two. > > # Use a separate prompt later in the form > constraint="/data/userEnteredPrompt != /data/calculatePrompt"/> > > # Compare when user is entering data > > > On Thu, Dec 6, 2012 at 7:45 AM, techbyte <techb...@gmail.com > wrote: > > 1) How many question questions ODK collect can support? > > > > 2)I want to match two fields 1)User Entered 2)Calculated. Until they > both > > do not match, user should not move ahead in form. > > > > Regards > > techbyte > > >
4

Give a man a fish and you feed him for a day. Teach a man to fish and
you feed him for a lifetime.

http://opendatakit.org/help/form-design

··· On Thu, Dec 6, 2012 at 8:08 AM, techbyte wrote: > Scenario is like this, > > Step 1: Prompt > Enter Retail Sale: > > Step 2: Prompt > Enter Retail Sale for Segment 1: > Step 3: Prompt > Enter Retail Sale for Segment 2: > Step 4: Prompt > Enter Retail Sale for Segment 3: > > Step 5: Total Segment Wise Sale = Retail Sale for Segment 1 +Retail Sale for > Segment 2 + Retail Sale for Segment 3 > > Check Total Segment Wise Sale == Retail Sale, if not matches show warning > and do not move ahead. > > How do i show calculated field on screen. > > Thanks > > > > > > On Thursday, December 6, 2012 9:27:50 PM UTC+5:30, Yaw Anokwa wrote: >> >> 1. Depends on how many languages, how much relevancy, and how much RAM >> is in your device. I've seen usable surveys with a few thousand >> prompts. >> >> 2. Put a constraint that compares the two. >> >> # Use a separate prompt later in the form >> > constraint="/data/userEnteredPrompt != /data/calculatePrompt"/> >> >> # Compare when user is entering data >> >> >> On Thu, Dec 6, 2012 at 7:45 AM, techbyte wrote: >> > 1) How many question questions ODK collect can support? >> > >> > 2)I want to match two fields 1)User Entered 2)Calculated. Until they >> > both >> > do not match, user should not move ahead in form. >> > >> > Regards >> > techbyte >> >
5

There's a thread in one or the other groups that cites the hardware
requirements guides for Android devices which is useful to be aware of.
Basically, the higher resolution and bigger screen devices are required to
have more memory capacity for apps.

··· On Thu, Dec 6, 2012 at 8:09 AM, Yaw Anokwa wrote:

Give a man a fish and you feed him for a day. Teach a man to fish and
you feed him for a lifetime.

http://opendatakit.org/help/form-design

On Thu, Dec 6, 2012 at 8:08 AM, techbyte techbyte101@gmail.com wrote:

Scenario is like this,

Step 1: Prompt > Enter Retail Sale:

Step 2: Prompt > Enter Retail Sale for Segment 1:
Step 3: Prompt > Enter Retail Sale for Segment 2:
Step 4: Prompt > Enter Retail Sale for Segment 3:

Step 5: Total Segment Wise Sale = Retail Sale for Segment 1 +Retail Sale
for
Segment 2 + Retail Sale for Segment 3

Check Total Segment Wise Sale == Retail Sale, if not matches show warning
and do not move ahead.

How do i show calculated field on screen.

Thanks

On Thursday, December 6, 2012 9:27:50 PM UTC+5:30, Yaw Anokwa wrote:

  1. Depends on how many languages, how much relevancy, and how much RAM
    is in your device. I've seen usable surveys with a few thousand
    prompts.

  2. Put a constraint that compares the two.

Use a separate prompt later in the form

Compare when user is entering data

On Thu, Dec 6, 2012 at 7:45 AM, techbyte techb...@gmail.com wrote:

  1. How many question questions ODK collect can support?

2)I want to match two fields 1)User Entered 2)Calculated. Until they
both
do not match, user should not move ahead in form.

Regards
techbyte

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com