Question Alessandro Venzi · Jun 30, 2016

WinSQL and HealthShare 2015.2: unable to see tables through catalogue and intellisense

Hi, after installed Healthshare 2015.2, all the tables previously correctly listed working with Healtshare 2014.1 are NOT listed anymore. TrakCare tables are not listed in the catalogue, nor by the WinSQL Intellisense.

Does anybody know a trick or have a hint to resume this useful functionality back?  

Thanks.

Comments

Kyle Baxter · Jun 30, 2016

Have you tried refreshing the catalog?  If that doesn't work I suppose it could be a permissions issue.  If you want to pick up an ODBC log I'd be happy to review it.

0
Kyle Baxter · Jun 30, 2016

Have you tried refreshing the catalog?  If that doesn't work I suppose it could be a permissions issue.  If you want to pick up an ODBC log I'd be happy to review it.

0
Alessandro Venzi  Jun 30, 2016 to Kyle Baxter

Sure, I did.  Where can I get the ODBC log file? Thank you.

0
Kyle Baxter  Jun 30, 2016 to Alessandro Venzi

You can enable the ODBC log by going to the 32-bit Driver Manager (C:\Windows\sysWOW64\odbcad32.exe) and opening your DSN.  Click 'ODBC Log' which is a checkbox in the bottom-left of the screen.  Then open WinSQL, and refresh the catalog, and close WinSQL again (this last piece forces the log to flush out of buffers onto disk).  The log file will be in C:\Users\Public\Logs\CacheOBDC.log.

0
Alessandro Venzi  Jun 30, 2016 to Kyle Baxter

Did it. File has been uploaded. See on your right 

0
Kyle Baxter  Jun 30, 2016 to Alessandro Venzi

 Looking at the log I see:

DSN: TH_T2016_PRE-LIVE
    USERNAME: 

So you are logging in as unknownuser?  If so, does that user have permissions?  

0
Alessandro Venzi  Jun 30, 2016 to Kyle Baxter

No, Username and Password are correctly specified, in the Data Source details.

Don't know why 'USERNAME:'  is not correctly logged into file.

0
Timur Safin · Jun 30, 2016

So you are using ODBC access in WinSQL to connect to CacheODBC source, from particular namespace...

Did you check you are using DSN pointing to the desired namespace? Did you check the bitness (32- or 64-bit) for DSN you use in WinSQL? 

0
Alessandro Venzi  Jun 30, 2016 to Timur Safin

Connections are OK:

I can perform queries successfully for new Data Sources (created after installed HS2015.2) AND for the previously created Data Source ones (created before installed HS2015.2).

Now, as a side effect, I'm not able to view any table or fields  for  all Data Sources configured.

0