Thanks, I went through the options on the HS.ADMIN menu, including HS.SCRUB and the HS_FILE_ACCESS file was created. For some reason it excluded the file I need from HS_FILE_ACCESS though, even though I added an @SELECT dictionary item. If I run CONVERT.SQL against the file (not using my live data file), I can then see it via ODBC in Excel, but the dict items don't work correctly. Is it safe to manually add a record for the non-SQL file to HS_FILE_ACCESS?

Thanks,
John

Jeff Schasny wrote:

First create an @SELECT item in the dictionarys of the files you are aiming
at.

Then logto HS.ADMIN and issue the HS.ADMIN command from TCL.  Select Option
#3 to activate access to files in an account. Whenever you change an @SELECT
Item or want to add access to another file you can run HS.UPDATE.FILEINFO in
the account rather than going back to the HS.ADMIN account and running
option #4 (Update File Information Cache in an account).

-----Original Message-----
From: John Hester [mailto:[EMAIL PROTECTED]
Sent: Monday, February 16, 2004 3:34 PM
To: U2 Users Discussion List
Subject: UV: Enabling ODBC for non-SQL file


I'm trying to enable ODBC access to a standard UV non-SQL file and have found the following in the ODBC manual:


"To make UniVerse files accessible to ODBC applications, you must run the ODBC file access utility in the account."

However, they don't bother to say what this ODBC file access utility is called. I've tried listing the VOC LIKE ...HS... and ...MENU... but can't find anything relevant. Are they referring to HS.UPDATE.FILEINFO?

TIA,
John


-- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users

Reply via email to