Hi Maz,
I understand the problem you are having. TestStand uses Step.Limits.High(or Low) to store the limits of a numeric limit test, but uses Step.Result.Measurement[i].Limits.High(or Low) to store the limits in a multiple numeric limit test. The i is the index of each measurements in your step.
You don't need to have more that one record in your database for a multiple numberic limit test, instead, you need to have more columns in your table so that you can store the limits for every measurement in your test. I know it doesn't sound like the best design, but that's the way it is. Your table needs to have columns called for example Result_1_Limits_High_N, Result_2_Limits_Low_N, etc.
Now, how do you confgure this in Teststand? When you select th
e properties you want to import in your property loader, make sure you include Step.Result.Measurement[i].Limits.High(and Low) and map the property to the columns in your table.
Something you can do, is use the property loader from the tools menu in teststand. Select your database, make the SQL statement something like: "SELECT Table1.* FROM Table1". Make sure the properties are selected and click on create columns. This will create columns in your database table.
I hope this helps, good luck.
Marcela.