On 15/02/14 19:05, Chris Austin wrote:
> I guessing could do all that.. OR have excel refresh the tables when u
> connect...
>
> Maintaining separate tables just for ODBC is silly
Some of us learnt the *hard* way that it's a GOOD idea to have separate
dictionaries. HyperStar wasn't the most bug-
Our main production account has over a 1,000 files with roughly 31,000
dictionary items.
Running HS.UPDATE.FILEINFO would be problematic, at least that was our
experience.
We're running 11.1.13 which is fairly current.
-Troy
-Original Message-
From: u2-users-boun...@listserver.u2ug.o
We have a ton of I descriptors and it's quick when u set the option to refresh
in excel.. How many I descriptors do u gave?
> From: troy.b...@nordsonasymtek.com
> To: u2-users@listserver.u2ug.org
> Date: Sat, 15 Feb 2014 13:21:37 -0500
> Subject: Re: [U2] ODBC - Not finding the MV fields.
>
> I
I guessing could do all that.. OR have excel refresh the tables when u
connect...
Maintaining separate tables just for ODBC is silly
> From: troy.b...@nordsonasymtek.com
> To: u2-users@listserver.u2ug.org
> Date: Sat, 15 Feb 2014 13:21:37 -0500
> Subject: Re: [U2] ODBC - Not finding the MV field
I tend to agree with Bill with a similar approach of using a second ODBC
compliant dictionary.If you've tried running HS.UPDATE.FILEINFO on
dictionaries with complex I-descriptors, you find out that it churns forever
and doesn't come back.
To limit the ODBC visibility to what we need, we ha