![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi All, We have just beocme an OEM and will soon be upgrading our clients form SQL 8 to 11. This requires an "authenticated" database. We will modify our main appliction to execute the necessary authentication sql on the client side. Howerer, we have written several side applications using Access and InofMaker. What is the best way to connect to the database using these tools without forcing the end user to execute a "SET TEMPORARY OPTION" statement each time they run those side applications. TIA Mike |
#3
| |||
| |||
|
|
Will Access and Infomaker be updating the database? If so, you will need to add InitString=<set_connection_authentication_option> to the ODBC configuration (via the advanced tab Additional Connection Parms). If these are read-only, there will be no need to authenticate these connections using the most common OEM option. Mike Marston wrote: Hi All, We have just beocme an OEM and will soon be upgrading our clients form SQL 8 to 11. This requires an "authenticated" database. We will modify our main appliction to execute the necessary authentication sql on the client side. Howerer, we have written several side applications using Access and InofMaker. What is the best way to connect to the database using these tools without forcing the end user to execute a "SET TEMPORARY OPTION" statement each time they run those side applications. TIA Mike |
![]() |
| Thread Tools | |
| Display Modes | |
| |