Bugs and Known Issues

NASIS Client Version 6.1.1 - SVN Rev. No. 10050

Known Bugs

1. An error message like “Object reference error” may pop up when closing a table editor. This is most likely to happen with a table that has a lot of child tables (like Data Mapunit) because it takes longer to close, and it happens when the mouse is moved around while the table is closing. You can ignore this message.
    
2. In Local Database Setup it appears that data can be modified, but such changes are not saved anywhere. Local Database Setup should not be used to edit data.
    
3. In Local Database Setup and Select Table Layouts it is possible to move, hide or group columns, but these operations generally don’t make sense in that context and could be confusing.
    
4. In table editors the F4 key is supposed to open or close choice lists and other pop-up editing tools. This is not working for text fields. You have to click the button in the text field to see an editing window.
    
5. When using a tablet PC an on-screen keyboard normally appears when you start to edit a text field. This doesn’t happen with the new text edit pop-up box, so you will have to open the keyboard manually.
    
6. There is no Change Owner capability for Table Layouts.
    
7. The Export Explorer does not include a Delete option. To delete an old export, use a query to bring it into the selected set and open the Distribution Metadata table.
    
8. When viewing the Calculation table in the table editor, the column Base Table shows numbers instead of table names. Open the calculation editor to see the base table names.
    
9. When multiple items are selected in the Calculation/Validation Explorer the Run for All Rows in Selected Set option is not active in the right-click (context) menu. The option is available in the Calculation/Validation Explorer menu and toolbar.
    
10. Report output that appears in a browser is often hidden behind the NASIS window.
     
11. When you have messages in the status or validation list that include hot links, and you undock the message area, the links get changed to plain text.
     
12. When you check out a Table Layout, a link appears in the status message window to say that the record was checked out. Clicking on that link will produce an error message.
     
13. When creating a SSURGO export, on the Run Export tab a confusing error message is displayed when the Export File Name field is not filled in. It says “a well-formed output file name must be supplied and an export file name must be supplied” but the output file name and the export file name are the same thing. It should just say “a well-formed export file name must be supplied”.
     
14. In a SSURGO export the columns that contain decimal numbers typically have too many decimal places. This does not affect importing the data into MS Access.
     
15. When entering a note in the Dr. Nasis window the right-click editing functions don’t work.
     
16. When a NASIS data model change is made and you have left NASIS running on your computer, it will allow you to log in and continue working. But a download or refresh will probably fail due to the data model change. You have to exit from NASIS and restart, which will then force an initialization to the new data model.
     
17. When copying and pasting in text fields the Undo button may operate differently than you expect. Some inconsistent behavior has been seen.
     
18. If you select some rows in a table and do Change Owner but the rows are not checked out, the response is a little unclear. It says the operation was successful and 0 rows were changed.
     
19. In a SQL query in a report script you cannot use ORDER BY in a subquery, although that is allowable in standard SQL. That will be corrected in the next release.
     
20. In report and property scripts the ARRAYAVG function does not exclude null values as it should. Until this is fixed a workaround is an expression like ARRAYAVG(LOOKUP(NOT ISNULL(x), x)).