Your custom fields should work, but I think you may be missing something;
here are a few pointers - bear with me on the simple stuff as it may highlight something:
As cody84 said, the values still need to be entered into the value fields in the components table for Empower to calculate the Amount field. The referencing custom fields then use this Amount field with the factors entered into your component fields.
When referencing fields, the spelling and capitalisation must be correct. Your example should read Amount*stdweight in the custom field.
Your referencing custom field will be a peak type field and will be found in the peaks table (under the chromatogram in the review main window). The field will only be populated for standards or samples where you have filled a value for both your new component field and the value field as both are used. The new custom field does not alter the value reported in Amount.
As mentioned, you can also use the SampleWeight and Dilution fields that are sample fields built into Empower. These alter the Amount returned by Empower.
For Standards: The software will divide the standard amount or concentration values by the Dilution field and multiply the amount or concentration values by the SampleWeight field (entered for that standard).
For Samples: The reverse is the case. The software will multiply the sample amount or concentration from the calibration curve by the Dilution field and divide the amount or concentration from the calibration curve by the SampleWeight field (entered for that sample).
SampleWeight and Dilution fields were originally designed to be used for samples or standards to account for dilution and sample losses, but you can use them as factors as you see fit.
If all the above is OK and you’re still not getting values, then troubleshoot your field by starting very simply. Create reference fields:
Amount (to double check your reference to this field),
stdweight (to double check your reference to this field),
and then
Amount*stdweight
If that does not work… drop me a line
ben.w@mvc-consult.com and we can see what is wrong…