Announcement
Collapse
No announcement yet.
SQL Server Login Dialog box
Collapse
X
-
I agree with Geoffww that the Application Name on the SQL Server login dialog should follow the installer's configured Product Name.
-
Correct I do suppress the dialog box with hide, but it might be helpful to have as "auto" in case the connection credentials fail, then the user could get the dialog box with other options. Anyway no worries. Thanks.
Leave a comment:
-
I do not believe that the SQL Server login dialog can be customized. You can suppress it completely, passing the parameters SERVER, UID, PWD etc. in the connection string, and setting the second parameter of ODBC.OpenDirectConnection() to "hide".
Ulrich
Leave a comment:
-
True. However, since "Setup Factory" doesn't appear in any screen in my installer I don't think it should be here. Can it be suppressed? From the end user's perspective what is running is "X company's installer" not really "Setup Factory" even though technically it is Setup Factory's exe. Why would the end user need to have this field present on this dialog box?
Thanks.
Leave a comment:
-
I would say that it is not your product which is running, but the runtime engine of the installer of your product. The name of the application attempting to access the SQL server is correct in this context, isn't it?
Ulrich
Leave a comment:
-
SQL Server Login Dialog box
See attached image. How do I remove or change the wording in this dialog box for the Application Name? It says Setup Factory Runtime. Shouldn't it have the name of my application name from %ProductName%.
Thanks.1 PhotoTags: None
Leave a comment: