Creating a drop box or Dlook up

[kbrown9]

Hello all,
Any assistance will be appreciated. I'm new to InfoPath...Much thanks
in advance. I have Microsoft Access database that has id numbers (for
example 1234)...since id number have to be unique...it is very common
that a survey will have the same id number...so when this occurs...we
assign the survey id number a letter (a-z..like 1234a)...how can I
build a function that will show the next available letter...right now
we printout a document daily that listed all used id numbers...this is
a large printout (it has over 15,000 cases)...I'll be thankful for any
help or suggestions on how I should approach this matter...in summary
if the id number 1234a, 1234b, 1234c and 1234d are in the database...I
would like the the unbound/dlook box or the drop-down to show the next
available letter...1234e.

 

[dsc2bjn]

I am fairly new to InfoPath and not familiar with your overall process, but I
don't think I would allow the lettering to take place.

I would push over the Unique Key value to the form as a Read-only value.
I would create a new field in both the Access Database and Info-Path form
which would create a unquie value for the form submissions. That way one
Access record could have many completed forms associated with it.

Each two field combination would be unique; therefore, you wouldn't need to
worry about the next value in a series.

Example:

AccessID: 1234
Form1ID: 1
Form2ID: 2

AccessID: 2345
Form1ID: 3
Form2ID: 4

Store the "Survey" questions in one table and the Survey results in another.
The SurveyID (from the Survey Questions table) field would be a look-up field
in the Survey results table.

 

[kbrown9]

Thanks, this is helpful.

I am fairly new to InfoPath and not familiar with your overall process, but I
don't think I would allow the lettering to take place.

I would push over the Unique Key value to the form as a Read-only value.
I would create a new field in both the Access Database and Info-Path form
which would create a unquie value for the form submissions. That way one
Access record could have many completed forms associated with it.

Each two field combination would be unique; therefore, you wouldn't need to
worry about the next value in a series.

Example:

AccessID: 1234
Form1ID: 1
Form2ID: 2

AccessID: 2345
Form1ID: 3
Form2ID: 4

Store the "Survey" questions in one table and the Survey results in another.
The SurveyID (from the Survey Questions table) field would be a look-up field
in the Survey results table.