This problem appears when a population has been replaced on a PC normally set to a language other than English. This issue is similar to #1021, except that the exact problem cannot be pinpointed.
Problem Description
The application will start and works normally while inputting parameters in a scenario. The exception is on the Disease Spread tab. At the bottom, there is a section for disease spread assignments. This allows you to indicate the source production type and the destination production type for movements. When this issue is occurring, no production types will be visible, and therefore an assignment cannot happen. The validation tab color will stay yellow. If you attempt to validate scenario, an error indicating production type has not been assigned, and will not participate in the spread will be shown.
Solution
This issue has had limited testing by the ADSM Development Team. We have had success when starting a new scenario without using the replace population. This may cause additional work but is a solution. Recall that both types of functions can be exported from a non-working scenario and imported into a new scenario to avoid creating functions a second time.
This problem appears when a population has been replaced on a PC normally set to a language other than English. This issue is similar to #1021, except that the exact problem cannot be pinpointed.
Problem Description
The application will start and works normally while inputting parameters in a scenario. The exception is on the Disease Spread tab. At the bottom, there is a section for disease spread assignments. This allows you to indicate the source production type and the destination production type for movements. When this issue is occurring, no production types will be visible, and therefore an assignment cannot happen. The validation tab color will stay yellow. If you attempt to validate scenario, an error indicating production type has not been assigned, and will not participate in the spread will be shown.
Solution
This issue has had limited testing by the ADSM Development Team. We have had success when starting a new scenario without using the replace population. This may cause additional work but is a solution. Recall that both types of functions can be exported from a non-working scenario and imported into a new scenario to avoid creating functions a second time.