A parent table creates sequentially numbered sample names (e.g. Sample34, Sample35, ..., Sample42) that are stored in separate records along with other descriptive data (essentially duplicated data with the exception of the unique sample names). The user determine the number of sample names by entering the number of sample replicates. A daughter layout must show these sample names on one side of the screen so that a user can copy and paste these sample names from the list into a portal on the other side of the screen that is designed to simulate a 9x9 grid storage box (i.e. one sample name per position in box). This would allow us to keep track of where samples are located. BTW, each sample box is uniquely identified.

A portal doesn't work here because the data comes from a parent. A repeating field doesn't work well because I don't think you can populate it from within a script in the parent table by using a Set Field[ParentTable::RepeatField[Ctr]; SampleName] where Ctr represents a variable counter providing the indexing and SampleName is constantly updated through each pass in the loop.

It seems my table organization is poor, but it appears to simulate what goes on in the real world. Any help for a desperate novice? Did I say desperate. I meant REALLY desperate!

A parent table creates sequentially numbered sample names (e.g. Sample34, Sample35, ..., Sample42) that are stored in separate records along with other descriptive data (essentially duplicated data with the exception of the unique sample names). The user determine the number of sample names by entering the number of sample replicates. A daughter layout must show these sample names on one side of the screen so that a user can copy and paste these sample names from the list into a portal on the other side of the screen that is designed to simulate a 9x9 grid storage box (i.e. one sample name per position in box). This would allow us to keep track of where samples are located. BTW, each sample box is uniquely identified.

A portal doesn't work here because the data comes from a parent. A repeating field doesn't work well because I don't think you can populate it from within a script in the parent table by using a Set Field[ParentTable::RepeatField[Ctr]; SampleName] where Ctr represents a variable counter providing the indexing and SampleName is constantly updated through each pass in the loop.

It seems my table organization is poor, but it appears to simulate what goes on in the real world. Any help for a desperate novice? Did I say desperate. I meant REALLY desperate!

A parent table creates sequentially numbered sample names (e.g. Sample34, Sample35, ..., Sample42) that are stored in separate records along with other descriptive data (essentially duplicated data with the exception of the unique sample names). The user determine the number of sample names by entering the number of sample replicates. A daughter layout must show these sample names on one side of the screen so that a user can copy and paste these sample names from the list into a portal on the other side of the screen that is designed to simulate a 9x9 grid storage box (i.e. one sample name per position in box). This would allow us to keep track of where samples are located. BTW, each sample box is uniquely identified.

A portal doesn't work here because the data comes from a parent. A repeating field doesn't work well because I don't think you can populate it from within a script in the parent table by using a Set Field[ParentTable::RepeatField[Ctr]; SampleName] where Ctr represents a variable counter providing the indexing and SampleName is constantly updated through each pass in the loop.

It seems my table organization is poor, but it appears to simulate what goes on in the real world. Any help for a desperate novice? Did I say desperate. I meant REALLY desperate!

Your script can have 9 steps for set field, as follows

Set Field [ ParentTable::RepeatField[1]; GetField ("SampleNameTextPart"&StartNum)

Set Field [ ParentTable::RepeatField[2]; GetField ("SampleNameTextPart"&StartNum+1)

Set Field [ ParentTable::RepeatField[3]; GetField ("SampleNameTextPart"&StartNum+2)

...

Set Field [ ParentTable::RepeatField[9]; GetField ( "SampleNameTextPart"&StartNum+8)

This is instead of looping and relying on a calculation for Set Field, which you can't do anyway.

Your script can have 9 steps for set field, as follows

Set Field [ ParentTable::RepeatField[1]; GetField ("SampleNameTextPart"&StartNum)

Set Field [ ParentTable::RepeatField[2]; GetField ("SampleNameTextPart"&StartNum+1)

Set Field [ ParentTable::RepeatField[3]; GetField ("SampleNameTextPart"&StartNum+2)

...

Set Field [ ParentTable::RepeatField[9]; GetField ( "SampleNameTextPart"&StartNum+8)

This is instead of looping and relying on a calculation for Set Field, which you can't do anyway.

A portal doesn't work here because the data comes from a parent.

Could you exactly elaborate on this because this shouldn't be a problem.

A portal doesn't work here because the data comes from a parent.

Could you exactly elaborate on this because this shouldn't be a problem.