Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello:
I've QV Desktop 11 SR2 on a local x64 computer, I'm trying to write back to a MS-Access 2010-DB (32 bits) and always get this error:
"Provider cannot be found. It may not be properly installed."
This is the code on the QV-Macro
Dim objADO
Dim objRs
Dim sConn
Dim strSQL
' Create ADO Object ...
Set objADO = CreateObject("ADODB.Connection")
' Set the conection parameters
Provider = "Microsoft.ACE.OLEDB.12.0"
Server = "D:\Backend Publisher\Desarrollo\Compartidos\Datos\"
DB = "QV_Config.mdb"
Uid = "Admin"
Pwd = ""
CreateObject("ADODB.Connection")
With objADO
.Provider = Provider
.ConnectionString = "Server=" & Server & _
";Database=" & DB & _
";Uid=" & Uid & _
";Pwd=" & Pwd & ";"
.CursorLocation = 3
.Open
End With
Of course, the jet is installed and works fine, this is the OLEDB connection that work on the script,
' OLEDB CONNECT32 TO [Provider=Microsoft.ACE.OLEDB.12.0;User ID=Admin;
' Data Source=D:\Backend Publisher\Desarrollo\Compartidos\Datos\QV_Config.mdb;
' Mode=Share Deny None;Extended Properties="";Jet OLEDB:System database="";
' Jet OLEDB:Registry Path="";Jet OLEDB:Database Password="";Jet OLEDB:Engine Type=5;
' Jet OLEDB:Database Locking Mode=1;Jet OLEDB:Global Partial Bulk Ops=2;
' Jet OLEDB:Global Bulk Transactions=1;Jet OLEDB:New Database Password="";
' Jet OLEDB:Create System Database=False;Jet OLEDB:Encrypt Database=False;
' Jet OLEDB:Don't Copy Locale on Compact=False;Jet OLEDB:Compact Without Replica Repair=False;
' Jet OLEDB:SFP=False;Jet OLEDB:Support Complex Data=False];
I've selected System Access and Allow System Access on the Edit Module security setup.
I don't know what I'm doing wrong?
Thank you
Somewhere on the internet I've read "not literally" that to do this is necessary MS-Access x64 or downgrade QV to 32bits
Somewhere on the internet I've read "not literally" that to do this is necessary MS-Access x64 or downgrade QV to 32bits
QlikView doesn’t support direct writeback to databases like MS Access through standard ODBC connections, which is why you’re running into this issue.
To achieve this, you usually need an external layer (macros, APIs, or extensions).
Alternatively, using a structured writeback solution like SenseOps can help handle database
updates in a more controlled way without relying on unsupported direct connections. Know More>>