SLXOLEDB Provider connection string in 9.4 and beyond

scottsommerfeldt

Hey Team

Seems as of 9.3 and beyond the SLXOLEDB Provider Connection string has changed or is no longer working.

I have tried the old method of creating a udl file ensuring to use a 32bit provider, but it always fails authentication even though I know the password is correct.

Has this changed? Is it possible to keep old applications working using the SLXOLEDB Provider? for 9.4 and beyond.

Here is a sample of my connection string. maybe I am missing something.

Provider=SLXOLEDB.1;Password=<PASSWORDHERE>;Persist Security Info=True;User ID=admin;Initial Catalog=SALESLOGIX;Data Source=INFOR94SERVER;Extended Properties="PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1;SVRCERT=;"

Thanks,

Scott Sommerfeldt

cgrant

Hi Scott,
In 9.4 they went through and encrypted password correctly. As a result tth econnection string is expecting the encrypted version of your password.

2 Options.

1. You can find the conenctionstring to the users you want to connect with by temporarily adding the following line into Lan Client Account Detail Form in AXFormChange
   MsgBox Application.ConnectionString
   Then log in as the users you want to use. You will see the connection string currently being used.
2. Change your connection string to use Windows Auth. NB YOU will need to associate the user you want to login as to the Windows Account and also turn on Windows Authentication (See Admin Application. Tools —> Options… —> Password. Top option). NB In Lan Client if users do not have Windows accounts associated to them they can still log in with the SLX credentials.
   Provider=SLXOLEDB.1;Integrated Security=True;Data Source=<SERVER NAME>; Initial Catalog=<DATALINK NAME>; Extended Properties=PORT=1706;LOG=ON;Location=;Mode=ReadWrite

Cheers
Chris