I would question the "requirement" to place the data into one field. I would think that something like this would make more sense: <Parent Record> Test_Type
Based on test type 1 or more child records containing the value(s) you need to store ex: Test_Type_1 (needs 3 result values) Result1 : 5 Result2 : 3 Result3 : 12.3 To make this flexible for the user, you can create a Test Setting record (for each test type) This would minimally contain: Record ID Test type - this is what you would use for a lookup Number of results required the users can then create/change/delete (only if the test type was never used) the test definitions as their requirements change Chip > Hi All, > > I use 4D v16. > > I've needed to save more values of the same type (more results for one test) > > The number of values to save, must be variables based on test type, > and all values must be saved into the same record. > > Until now I use one text field and separated from one character so: > val1;val2;val3 > > Does someone have a suggestion to improve this solution? > > Thanks > > Ferdinando > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > New Forum: https://discuss.4D.com > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:4d_tech-unsubscr...@lists.4d.com > ********************************************************************** ------------ Hell is other people Jean-Paul Sartre ********************************************************************** 4D Internet Users Group (4D iNUG) New Forum: https://discuss.4D.com Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
