Reply to thread

Message

<blockquote data-quote="jimbolina" data-source="post: 175072" data-attributes="member: 54521">The new fix works good for me. Cheers! <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Another bug though...On the configuration screen, if you select &quot;mssql&quot; before entering the parameters, it tries to connect anyway and eventually throws a &quot;cannot connect to database&quot; error but this error is in the background and you need to alt-tab to click ok and make it go away. If you don't alt-tab, the program doesn't respond to any clicks and would appear to be frozen (but it is just the error dialog in the background locking the program).If you do find the dialog and click ok, you can setup the program and load the data fine, but after you close it, you will get the windows error reporting dialog a few seconds later. If you then run the program again, it opens and connects fine and when you close it there is no error (because the login data is already stored I guess).So my guess for a fix is to stop it from trying to connect on selection of &quot;mssql&quot; and only connect when you click the connect button. Or maybe just implement a test to see if the login data is != null before trying to connect?</blockquote>

[QUOTE="jimbolina, post: 175072, member: 54521"] The new fix works good for me. Cheers! :) Another bug though... On the configuration screen, if you select "mssql" before entering the parameters, it tries to connect anyway and eventually throws a "cannot connect to database" error but this error is in the background and you need to alt-tab to click ok and make it go away. If you don't alt-tab, the program doesn't respond to any clicks and would appear to be frozen (but it is just the error dialog in the background locking the program). If you do find the dialog and click ok, you can setup the program and load the data fine, but after you close it, you will get the windows error reporting dialog a few seconds later. If you then run the program again, it opens and connects fine and when you close it there is no error (because the login data is already stored I guess). So my guess for a fix is to stop it from trying to connect on selection of "mssql" and only connect when you click the connect button. Or maybe just implement a test to see if the login data is != null before trying to connect? [/QUOTE]

Verification