Connection String to Silent ODBC DSN using ProvideX ODBC Driver is forcing connection to default to SOTAMAS90 DSN

Question

We are querying invoice data to read from MAS using the ProvideX ODBC driver from within a custom application. Within the custom application, we have tried specifying credentials explicitly within the connection string used to open the ODBC connection but we are finding that the driver appears to be using the default SOTAMAS90 DSN even when we specify a different Silent Connection ( https://support.na.sage.com/selfservice/viewContent.do?externalId=19495&sliceId=1 ) DSN or specify a connection string that doesn't specify a particular DSN but does supply credentials. This is a problem because any time the Sage application is launched from the same workstation, the saved credentials within the ODBC connection for the SOTAMAS90 DSN get cleared out and the user is prompted for this login information at runtime when running the custom application. if we edit the SOTAMAS90 DSN by supplying it with valid user credentials the problem goes away and the user can run our custom application without being prompted, but as soon as Sage is relaunched the credentials get cleared out again and the user gets prompted once again. How can we establish a connection string within our application to the Silent Connection and have it actually connect to the Silent Connection and not the default SOTAMAS90 DSN?

David Speck · Answer

If your custom application can access user DSNs, you should be able to pass it the following connection string. 
 DSN=SOTAMAS90;UID=user;PWD=password;Company=ABC; 
 
 If it can't access user DSNs then you can always have it create a system DSN by writing to the registry but this would require elevated rights. You would just copy the contents of the user DSN to the system DSN so the paths are correct. You can then optionally set specific options for your system DSN. 
 If you don't want to use "DSN=" in your connection string, you could instead use "driver={MAS 90 4.0 ODBC Driver}" followed by all the required parameters. I prefer using the DSN route since i won't have to worry about paths. As long as the workstation is updated during the upgrades or server moves, the user DSN named SOTAMAS90 should always have the correct paths and default options.

TPeterson · Answer

It's been some time since I've worked with VB6, but the following code snippet is what we used to use in our VB.NET apps when accessing Sage data.. It dynamically builds a connection string depending on if the install is Standard or Advanced (C/S). 
 Perhaps, you can re-tool it to fit in VB6. 
 
 Dim constr As String = "" 
 If CBool(My.Settings.CS) Then constr = constr & "DSN=SOTAMAS90; Directory=" constr = constr & My.Settings.SageInstall constr = constr & "; Prefix=" constr = constr & My.Settings.SageInstall constr = constr & "\SY\, " constr = constr & My.Settings.SageInstall constr = constr & "\==\; ViewDLL=" constr = constr & My.Settings.SageInstall constr = constr & "\HOME; LogFile=\PVXODBC.LOG; RemotePVKIOHost=" constr = constr & My.Settings.SageServerName constr = constr & "; RemotePVKIOPort=" constr = constr & My.Settings.SagePort constr = constr & "; CacheSize=4; DirtyReads=1; BurstMode=1; StripTrailingSpaces=1; SERVER=NotTheServer" constr = constr & ";UID=" & My.Settings.SageUserName & ";PWD=" & My.Settings.SagePassword & ";Company=" & CompanyCode Else constr = constr & "DSN=SOTAMAS90; Directory=" constr = constr & My.Settings.SageInstall constr = constr & ";UID=" & My.Settings.SageUserName & ";PWD=" & My.Settings.SagePassword & ";Company=" & CompanyCode End If 
 Dim con As System.Data.Odbc.OdbcConnection = New Data.Odbc.OdbcConnection(constr)

Sage 100

Connection String to Silent ODBC DSN using ProvideX ODBC Driver is forcing connection to default to SOTAMAS90 DSN

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING