Re: [U2] ODBC - Not finding the MV fields.
Chris Austin <[email protected]> Fri, 14 Feb 2014 08:53:03 -0600
| Newsgroups | gmane.comp.db.u2.general |
|---|---|
| Message-ID | <[email protected]> |
I found the answer in case anyone stumbles upon this. In Excel, under "UniVerse ODBC Data Source Setup" there's a radio button that's defaulted to "Fast Connect (Old OTL)". This was the problem.. When you bring MultiValue fields into ODBC it treats them like tables and you need to have refresh your environmental variables for them to be picked up after you setup an association. THE SOLUTION = check the radio button "Refresh OTL on Connect". I believe we needed this with UniVerse 11.x and up. FROM THE DOCS: Fast Connect (Old OTL) – This option applies only to UniVerse files that are not tables. When you select this option, the ODBC table list is not refreshed in memory, and the File Information Cache is read from disk and used instead. This option may result in faster connect times, but possibly in a less up-to-date list of available tables.Note: The HS_USE_FILEINFO environment variable has no effect at UniVerse 10.2. Refresh OTL on Connect – This option applies only to UniVerse files that are not tables. When you select this option, the ODBC table list is queried. This operation may impact initial connect time. The File Infor-mation Cache is not updated by the operation. Update the cache by running HS.UPDATE.FILEINFO in the UniVerse account you are accessing on the server system > From: [email protected] > To: [email protected] > Date: Thu, 13 Feb 2014 15:04:09 -0600 > Subject: [U2] ODBC - Not finding the MV fields. > > We're running UniVerse 11.x and we've had ODBC setup for a while but recently started to use it more. The single-value fields work just fine, but on some of the Multi-Value fields (only certain tables) we can get the ODCB to work in excel by manually entering the SQL command but they don't show in Microsoft Query. > > So the issue is that we don't see it in the Microsoft Query window, or even in Access (for certain tables). Is there anyway to "debug" why the MV on some tables > work, but others don't? Is there a way to list the tables that ODBC recognizes? > > I tried using Dr. DeeBee and it wasn't much help since I didn't get a log after running it. > > Any help is appreciated, thanks. > > Chris > > > > > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users