Hello Everyone, this might be long. I have an old, and fairly large, Visual FoxPro application that uses an on premise SQL Server as the backend. The application uses remote views that rely on ODBC DSN connections. I moved the database to Azure and it worked well for a while...until the demise of ADAL last December. I can create 64 bit ODBC DSN connections but 32 bit, which is what FoxPro can use, fail to connect. Other than recreating the application in another language, have anyone found a workaround for this?

Hello,

MSAL does not support 32 bits?

https://learn.microsoft.com/en-us/azure/active-directory/develop/msal-migration

Thanks Carlos, that's correct, FoxPro cannot use MSAL. So what is the correct path to keep this type of applications running, besides re-writing them in another language?

Can't you use the standard SQL driver for Azure? It'll work with just about everything except some of the Azure specific types and newer SQL Server features.

+++ Rick ---

Thanks Rick, I'm trying to avoid the user having to enter their user name and password, this system has dozens of apps, each app with its own remote view, since they have private data session each time they open a new app I'm afraid they will have to enter again their credentials, for now I'm Ok since we are running an on-premises server and I'm using 'Windows authentication" to connect to it, I'm just trying to not get caught without options in the future.

Not sure what you're saying. You provide a connection string with credentials, or token from Azure I believe. I haven't done this in a long while but when I tried this it works.

I can't speak to Windows or Azure AD auth, but I doubt that would work with off Azure clients either way. If you're offline you need to use connection strings with credentials or security tokens.

+++ Rick ---