how to would this be set?

[icemonster]

so i have this connection settings each time i update, insert, delete something in my record though i realized when the application is placed in our LAN server i would have to change the user and password as well as host, is there a way or how would this be set each time the application starts? and checks whether the connection is valid?

      Set cnx = New ADODB.Connection
      With cnx
          .Open "DRIVER={MySQL ODBC 3.51 Driver};" & _
                "Server=myServerName;" & _
                "Port=3306;" & _
                "Option=16384;" & _
                "Stmt=;" & _
                "Database=mydatabaseName;" & _
                "Uid=myUsername;" & _
                "Pwd=myPassword" 

      End With
      Set cnx = Nothing

 

[mdlueck]

So how are you thinking to obtain the ID/pw? Force the user to authenticate again with your application?

I have code which runs through Linked-Table objects and updates the connection string. Without calling that code, the Linked-Table objects may not be opened, once run they may be.

As well I use the id/pw to crate an ADO.Connection object and leave that object floating around the application in global variable space. When ever ADO objects are crated, that Connection object is referenced and provided to the new ADO object.

My application happens to use a single ID to connect to SQL Server, and I have come up with my own authentication scheme to provide per-user permissions and transaction logging. Users are not prompted to log in a second time to the application as the assumption is made that who ever is signed into Windows / AD is also using the application.

 

[icemonster]

am thinking of storing it? but a lot of people told me it's a bad idea. not sure though. but what am really concerned in doing here is how would the server and the database be set each time the application is deployed to a new computer? the user name and password i can store it if i have to but what about the server location? before, we considered getting a vps which was easy cause all i had to do was set the DNS but now they "changed" their mind and wanted to do it over LAN which frankly i am not sure how to do it. do i set up the ip each deployment?

 

[mdlueck]

Sounds like you have acute blank-chalk-board-itus. There are various ways to provide authentication / single sign-on capabilities. Each scenario will have a different amount of risk to balance the ease for end-user use.

Perhaps start with a list of must-have requirements (such as is one known ID acceptable to the SQL back end, or is a per-user ID a requirement) and start there for the discussion point.