View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002638||2 - Next Dev List (Holding Area)||Bug||public||2018-03-29 20:19||2020-07-02 02:13|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0002638: Logbook: "Network Server" configuration is not updated when a database configuration is deleted|
The Logbook has a configuration which selects a default database for network operations, like the HRD CLI, or communications from other applications like DM780. It's possible for the user to delete the database configured as the default for Network SErver operations; the application doesn't notice this condition, silently fails calls, and causes trouble for users.
|Steps To Reproduce||1) Open the Logbook. Make sure you have a spare database available.|
2) Use the "Network Server" command in the "Configure" menu.
3) In the "Database" dropdown of the "Network server" dialog, select your spare database by name.
4) Press "OK" to exit the dialog.
5) Fire up DM780.
6) Use the ALE in DM780 to try to query or add a callsign to your log. Works fine.
7) Go back to the logbook. Right-click on the list of databases, which brings up the ODBC configurations for the logbook databases.
8) Select your spare, currently open database.
9) Press the "Delete" button.
10) In the resulting prompt, indicate that you do indeed want to delete the data source configuration.
11) Go back to DM780. Try again to manage a callsign with the ALE.
BUG#1) It doesn't work.
12) Back to the Logbook. Again use the "Network Server" command in the "Configure" menu.
BUG#2) Note that the spare database _isn't_ selected, but the Logbook is still trying to talk to it by default.
|Tags||No tags attached.|