Ok, I wanted to give everyone the final outcome of this.  My last post had an issue regarding using msiexex but that was an issue on the computer, further testing on other machines did not have this problem.

When a user clicks the login button, after supplying ID and password, I check the  sqlca.sqldbcode for results.

If  sqlca.sqldbcode = 999 then the 64 bit drivers are missing.  I display an pop up window explaining the issue and telling the user to click Yes on both Regedit and MS OLE SQL Drivers when asked to modify the computer.  If we are missing the 64 bit drivers I run a BAT file that does the following.

rem regedit will only do an import from a REG file on the local drive

xcopy e:\rms\update_rms_cliconfig.reg c:\temp /y /j
c:
cd \temp
regedit.exe /s c:\temp\update_rms_cliconfig.reg

rem this will navigate to where my application is and run the smoledbsql program which is located in a sub folder sql_drivers

e:
cd \rms\rms-64
msiexec /i "sql_drivers\msoledbsql.msi" /passive IACCEPTMSOLEDBSQLLICENSETERMS=YES ALLUSERS=1

if sqlc.sqldbcode = 53 that means we have the 64 bit drivers but TCP and the alias for my SQL server was not configured in cliconfg.  In this case I run different BAT file that only has this code.

rem regedit will only do an import from a REG file on the local drive

xcopy e:\rms\update_rms_cliconfig.reg c:\temp /y /j
c:
cd \temp
regedit.exe /s c:\temp\update_rms_cliconfig.reg

I hope this will help others who are having this issue.

Here is an update to this, it worked on some test machines but now is not working on others.  Our network is simple, no Domain Controllers and the users log in with Administrator rights to their computers.  We can reformat the PCs if something is not working, easier this way for us. Anyway I now test for the drivers, if they are no installed I run the following.

ls_sql64 = 'msiexec /a "sql_drivers\msoledbsql.msi" /passive IACCEPTMSOLEDBSQLLICENSETERMS=YES ALLUSERS=1'
i = run(ls_sql64, Minimized!)

This runs the msiexec program as administrator and automatically accepts the terms.  

You see that it program starts and it is gathering data, then it just stops.  You think it is installed but it is not.  

I spent the day researching this and no one has reported this issue.  I even created log files and they report a success of 0 which means no errors according to the documentation.

Ok, so this is how I solved this problem.  When the user hits the login button, at the time I make the connect statement I check for the error of the missing drivers.

connect using SQLCA;
If sqlca.sqlcode < 0 Then
// test to see if the windows 64 msoledbsql.dll is missing, this creates the error sqldbcode = 999
if sqlca.sqldbcode = 999 then
   i = run("move_sql_dll.bat", Minimized!)
   Messagebox("Software Upgrade","Your computer is missing the Microsoft Software to connect to SQL Server. RMS will shut down, please try again AFTER     the MS Installation window disappears.",Information!,Ok!)
   disconnect;
   return
end if

I copied the installation MSI program in a subfolder called sql_drivers.  I call a BAT file located in the same directory as the application EXE.  The bat file has these commands

cd sql_drivers
msiexec /i "msoledbsql_V18.2.3.0.msi" /passive IACCEPTMSOLEDBSQLLICENSETERMS=YES
cd ..

The run function in PB returns a 1 for success in calling the BAT file, but that is it.  There is no way for me to wait for the install to finish and try connecting again, which is why I put up the Popup window.  After the SQL Drivers install the user can hit the login button again and get connected.

Not the cleanest method and I expect my users to call once they get the popup because they will not read it, but this is better than visiting all computers in the company and dealing with their login and such.

Hope this helps someone else.

NOTE: I changed the name of the msoledbsql program so I know what version we are loading.

One can only guess as to why Windows only uses this driver when it resides in the Windows System folder. Maybe because Microsoft considers it to be an "add-on" to the Windows O/S? What a PITA.

A clarifying note to others who may at some point refer to this thread: The following documentation on installing the OLE DB Driver for SQL Server:

   https://docs.microsoft.com/en-us/sql/connect/oledb/applications/installing-oledb-driver-for-sql-server?view=sql-server-ver16

clearly notes in the 2nd paragraph the different names of the system folder used for 64-bit apps and 32-bit apps:

The files for OLE DB Driver for SQL Server (msoledbsql19.dll/msoledbsql.dll, msoledbsqlr19.dll/msoledbsqlr.rll) are installed in %SYSTEMROOT%\system32\ . Additionally, the x64 msoledbsql.msi installs 32-bit binaries in %SYSTEMROOT%\SysWOW64\.

Of course, the current online documentation quoted above refers to Version 19 of MSOLEDBSQL, which will not be supported in PB until PB 2022 is released later this year. "%SYSTEMROOT%" refers to what on typical Windows installations is C:\Windows.

 A user requires Administrator privileges to manually copy files into the system folder(s). Presumably, the MSIEXEC utility can do so without Admin rights, but I've not verified this. The same URL listed above also describes how the MSIEXEC utility can be run silently, should you need to or wish to.

MSOLEDBSQL version 19 is supported by PB 2022 (in beta) even though the help file doesn't mention it as a new feature. 

I do not believe the MSOLEDBSQL driver needs/requires a registry entry, although they do make them during the install.  What I have found so far is that the file msoledbsql.dll MUST be in the windows\system32 folder, even if it EXISTS in the folder where the application resides.  This does not make sense to me as by default libraries are searched in the directy the application resided and then in the folders defined in the PATH environment.

Anyone have an idea why the DLL is not recognized in the application folder?  All of PB's DLLs are recognized in the application folder.

Thanks

Ok, so here is an update.  The latest version from MS does NOT work.  this version uses msoledbsql19.dll, which is a name change for the library.  We got this to work with version 18.2.3.0 of msoledbsql.msi.  When we run this install on a computer it works.

I would like to not have to install this on all computers.  So by copying the following 2 files into the folder that contains the application you can connect to the SQL server WITHOUT having to do individual install.  The 2 files are, msoledbsql.dll and msolesdbsql.rll.  msoledbsql.dll can be found in Windows\System32 and msolesdbsql.rll is located in Windows\System32\1033.

I hope this helps others.

Hey everyone, as stated I have this working on my local development PC.  I am stuck rolling this out to the clients.  I am definitely compiling using the 64 bit folder in PB.  I have also instaleld the 64 bit version of MSOLEDBSQL drivers.  After I install this driver I am still getting the error that this is missing.  I have a clean laptop that has all the most current MS Windows updates for version 10 and this is not working.

Thanks

Mike, this is really funny.  I started this program in 2001, and realized I wrote this error message.  Once I investigated the REAL error I was getting I discovered I was getting SQLSTATE = 08001.  This lead me to look into the cliconfig application.

The cliconfig application I was using was for 32 bit.  I did not have the cliconfig 64 bit version TCP enabled.  I now learned that the 32 bit version of cliconfig is in the windows\syswow64 and the 64 bit version is in windows\system32!  Makes perfect sense .

One weird thing is the network libraries in the 64 bit version for TCP/IP is c:\window\system32\dbnetlib.dll. Again this is confusing because it obviously is a 64 bit version residing in a 32 bit folder.

Thanks for all the help, at times you just need someone to help point you in some direction.

Are you using the 64-bit PB runtime DLL's when running the 64-bit compiled app? These reside in a different directory than the runtime DLL's used by a 32-bit compiled app and the PB IDE (which is also 32-bit).

The error I get when running the EXE is Connect to Database: Unable to Connect to Database either the ID or Password is incorrect.  But this works when I run the program from within PB.  This is also a generic issue if it cannot find a server.

I have installed the 64 bit drivers, I used the download from this page.

https://docs.microsoft.com/en-us/sql/connect/oledb/download-oledb-driver-for-sql-server?view=sql-server-ver16

still the same thing.  I downloaded the 64 bit driver, and for good measure recompiled and tried again.  Is there anything else I might be missing?

Hi Louis;

   You are probably missing the 64 bit SS DB Client drivers from Microsoft. The PB SS driver in the "X64" folder is only an "interface" to the real SS DB Client drivers. HTH

Regards ... Chris

did you install the 64 bit version of the MSOLEDBSQL database driver?

what is the error message you get?