Re: [U2] ODBC - Not finding the MV fields.

Chris:

1. The legacy dictionaries here tend to have overhead not needed by ODBC.
2. Only after experiencing some difficult ODBC problems here... and trying
to simplify the problem...  did I realize that some traditional DICT
characteristics are problematic to ODBC.
3. While having two dictionaries for the same data is not my first choice...
4. When it works... it is a beautiful thing.

--Bill

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Chris Austin
Sent: Friday, February 14, 2014 12:55 PM
To: U2 Users List
Subject: Re: [U2] ODBC - Not finding the MV fields.

Bill,

Not sure why you would do those 6 steps, when running HS.UPDATE.FILEINFO
from a command line or program will do the same thing (reset the cache w the
updated tables).

I like to limit the amount of dictionary entries I have.

Chris


> From: [email protected]
> To: [email protected]
> Date: Fri, 14 Feb 2014 12:37:29 -0500
> Subject: Re: [U2] ODBC - Not finding the MV fields.
> 
> Chris:
> 
> 1.  For things here, I usually create a new DICTionary... copy the old 
> DICT to the new DICT... and strip out NAME and other DICT columns not 
> needed by ODBC... in the new DICT.
> 2. A @SELECT of type PH is needed where the Phrase needs to specify 
> the chosen fields... in the new DICT 3. LOGTO HS.ADMIN.
> 4. Launch HS.ADMIN.
> 5. Run 6... Update File Info Cache in an account.
> 6. I hope that this helps.
> 
> --Bill
> 
>  
> 
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Chris 
> Austin
> Sent: Thursday, February 13, 2014 4:04 PM
> To: [email protected]
> 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
 		 	   		  
_______________________________________________
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