In message <[EMAIL PROTECTED]>, Bob Wyatt
<[EMAIL PROTECTED]> writes
Everything in VSG comes up fine; I can see all of the dictionary records I
want, and I add them to the table view and save the view.
When I do the database query from Excel, it only offers to import fields
0-5; none of the other defined fields in the view are in the list.
When I fire up the data warehousing application and do the ODBC SELECT, it
also only finds fields 0-5, and none of the other fields.
I haven't found anything in the UniData documentation that helps me figure
out why.
Do I need all of the fields defined contiguously (0 - 55)?
Or do you need to put the others back? I doubt it, actually :-)
You don't mention running something like HS.UPDATE. I'm *guessing* that
UD is similar to UV, and I'm *guessing* that what is happening is that
ODBC is going down its stored list of fields exporting them to Excel or
whatever, and it still remembers what was field 6. It hits it, errors,
and goes no further.
Not knowing UD, I don't know what VSG is. But on UV, ODBC is provided by
the old HyperStar (hence HS) software, and after editing the dictionary
you needed to rerun HS.UPDATE to get it to cache the new dictionary
definition. It seems to make sense that your export software still
remembers the old field 6, errors, and can't get past it.
Cheers,
Wol
--
Anthony W. Youngman <[EMAIL PROTECTED]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
