Where does QV pull ODBC info from when reloading?

[ellyodelly]

I have an app created locally using desktop.

Using QMC I have the app reloading hourly.

This app uses a ODBC on my desktop but the server where the QMC is running does not have the same DSN defined.

I need to repoint the ODBC, I have done so on my desktop but the QMC reload is still looking at the old location.

where do I find this mysterious link and how do I change it to the correct path?

[krishna_2644]

Hi - is there any 'include' statement in your script? or a script something like 'ODBC Connect32 bla bla' ?

[petter · Accepted solution]

You must log onto the server and run "ODBC Data Sources (64-bit)" and reconfigure your ODBC configuration. Afterwards you would need to go into the load script on the server and replace the connection string there with your newly defined configuration.

Alternatively you could:

• Change the connection string directly in your load scrirpt
• or export the ODBC setting from your desktop registry and import it on your server

[ellyodelly]

thank you-  but that is what is confusing me.

I don't see an original ODBC connection to modify on the server that is why I am not sure where QV is getting the connection information from.

I do not see an option for 64bit ODBC on my server-

but I will try the export-import and see if that works.

[ellyodelly]

I have a connect

ODBC CONNECT32 TO RITS;

[Peter_Cammaert]

Apparently your document is using a 32-bit ODBC connection whose definition is managed by an identical control panel but this one is compiled for 32-bit code.

You can start it by navigating to C:\Windows\SysWOW64 and from that directory you run the identically named program odbcad32.exe. That one manages just the 32-bit ODBC definitions.

[krishna_2644]

search for' 'ODBC Data Sources(32-bit)' in the windows search on the server, if you have access to else ask your admin to do so.

then go to 'User DSN'

If you sont see  'RITS', then ask your system admin to create a DSN connection on the server/new location and provide them the required credentials of the data source.once it is created, put that connection string in your qvw and try reloading from QMC do some basic verification.

[shilpan]

Or, you can open 32 ODBC connection panel from the script editor --> tools menu

[ellyodelly]

would I look under USER- not system?  but it is not in either-

it is alive!!!!!

no seriously- this is what is confusing me.

I did not get a chance today to try some of the other great suggestions-

I will work on squeezing some time in tomorrow.

but I do appreciate all the comments and thoughts.

it should be so black and white- but i know it usually is not- more so with connectors.

[petter]

Actually Microsoft has made this quite confusing. They have two ODBC Managers that looks very similar and depending on which version of Windows you are using the 32-bit or the 64-bit version you will get one or the other as default. On a 64-bit version of Windows you can run both ODBC Managers and configure both 32-bit and 64-bit ODBC drivers.

I don't know which version of Windows you are using?

Qlik Sense and QlikView are able to use both 32-bit and 64-bit drivers because Qlik has made an extra effort to be able to integrate more drivers.