Okay ... HS.FILE.ACCESS is the file used to define ODBC access rights to a non-sql account. It should be created automatically when you convert an account to ODBC access.
And HS.UPDATE.FILEINFO is that program that processes the HS.FILE.ACCCESS file. It creates some hidden file used by the odbc software so that it knows which files and fields it is supposed to make visible to an odbc client. So if you make any changes to the account from within UV, they are invisible to odbc until you update HS.FILE.ACCESS (if relevant) and rerun HS.UPDATE.FILEINFO Cheers, Wol -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Reid Sent: 27 January 2004 19:14 To: '[EMAIL PROTECTED]' Subject: RE: ODBC Set Up Universe Group, I had the trigger on a table on a development system until it got overwritten on the week-end. However, we never had a file named HS_FILE_ACCESS. I had created it, but I don't feel that its presence had much to do with whatever success I had. Is it supposed to 'MATERIALIZE'? My objective is to create a trigger on an existing file. Try as I might, I am unable to re-create what I did before. Could someone go over the steps one more time? And possibly, could someone state the function of the HS.UPDATE.FILEINFO? I'm not against reading what ever I need to read, but it seems that at least some people have had negative rewards for their reading efforts. thanks. john reid -----Original Message----- From: Tony Wood [mailto:[EMAIL PROTECTED] Sent: Thursday, January 22, 2004 5:57 PM To: [EMAIL PROTECTED] Subject: Re: ODBC Set Up Universe Anthony, Do you have NLS turned on? Does anyone have NLS turned on with ODBC on UniVerse? Regards, T. ----- Original Message ----- From: "Anthony Dzikiewicz" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 23, 2004 1:58 AM Subject: RE: ODBC Set Up Universe > Thanks for the replys on this issue. The problem was that I did a CREATE > SCHEMA in the account I was connecting to. I must have done this because I > was reading thru the ODBC guide and the SQL docs and merged the two in my > brain. Anyway, I guess if the account is a schema, then the files must be > present in the UV_TABLES file. So, my fix was to DROP SCHEMA in the > account. I then 'undid' the ODBC access and started from scratch without > the CREATE SCHEMA. Now, I can see the files. Now it is just a matter of > the HS_FILE_ACCESS and @SELECT that was mentioned. I placed a piece of red > tape over the CREATE SCHEMA button so this wont happen again. > Thanks > Anthony > > -----Original Message----- > From: Anthony Dzikiewicz [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 21, 2004 4:52 PM > To: [EMAIL PROTECTED] > Subject: RE: ODBC Set Up Universe > > OK I just got back to messing with the ODBC problem. There was one file in > particular that I was trying to make accessible called 'CR.TRANS'. I did > everything by the book and I still cant access it. As I mentioned, I didn't > see this file listed in UV_TABLES. There was a HS_FILE_ACCESS created in > the account. Anyway, I thought to just create a new file. So I did. I did > it thru the SQL command 'CREATE TABLE ANTHONY (MY_KEY PRIMARY KEY); I did a > HS.UPDATE.FILEINFO. I tried again via Microsoft query and I was able to see > ANTHONY with MY_KEY as a field. It worked ! I also noticed that UV_TABLES > has a new entry for this file. So, it looks like what I missed is the fact > that files that need to be accessible via ODBC should have entries in the > UV_TABLES file. Is this true ? If so, is there a utility that can get an > existing file added as a table ? Obviously, I cant CREATE TABLE to do this. > The file(s) already exist. Id rather not have to do REVISE UV_TABLES and > have to type everything manually. So, what did I miss in the part about > converting existing accounts into schemas ? Does any one know the magic > word to get existing files into the ODBC arena ? > Thanks > Anthony Dzikiewicz > > -----Original Message----- > From: Anthony Youngman [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 21, 2004 5:39 AM > To: [EMAIL PROTECTED] > Subject: RE: ODBC Set Up Universe > > And make sure that you don't have more files than you need in the > account. HS.SCRUB has a habit of abending without any errors (UV 9.6), > which can be a real pig when you're wondering why a certain file does > not appear to be exported ... there's a system multi-level file that > seems always to cause us grief. Can't remember what it's called - we > delete the voc pointer every time we see it - something to do with pterm > iirc. > > -----Original Message----- > From: Jeff Schasny [mailto:[EMAIL PROTECTED] > Sent: 20 January 2004 21:56 > To: [EMAIL PROTECTED] > Subject: RE: ODBC Set Up Universe > > Dictionarys of the files you wish to access must have an @SELECT "PH" > item > listing the fields that will be accessable in attribute 2 seperated by > spaces. Like this: > > DICT ENAMES 02:52:08pm 20 Jan 2004 Page 1 > > > > Type & > > Field......... Field. Field........ Conversion.. Column......... Output > Depth & > Name.......... Number Definition... Code........ Heading........ Format > Assoc.. > > > @ID D 0 ENAMES 10L > S > > NAME D 1 NAME 35L > S > > PW D 2 PW 12L > S > > @SELECT PH NAME PW > > When you get these items created you will need to execute the > HS.UPDATE.FILEINFO command from tcl. > CREATE.SCHEMA & SCRUB are nice but not necessary > > > -----Original Message----- > From: Anthony Dzikiewicz [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 20, 2004 2:39 PM > To: [EMAIL PROTECTED] > Subject: ODBC Set Up Universe > > > I need a push in the right direction on an ODBC config. I set up a test > machine with Universe on Red Hat. Everything is well and I am > attempting to > get ODBC going. This is new to me. We don't use this in the 'old' DG > system. So far I have done the following; I have the odbc driver going > - > it 'pings' it 'tests', did a su as uvsql and granted 'root' and > 'anthony' > DBA privilage. I logged into the account and did a CREATE.SCHEMA. I > though > that would be it. Cant connect - testing with excel. I read some more > manual. Logged into the HS.ADMIN account and did '3. Activate access to > files in an account', a world of messages went by stating how @select > doesnt > exist for file ....etc.. Don't know what that was all about, but excel > still > cant connect. I did a SCRUB on a small file to see if that would do it, > still not working. I did a update file information cache, still > nothing. I > am looking thru ODBC guide in the Universe docs. I must have missed > something. Ive also looked thru all the SQL manuals. So, how do I make > the > file accessible for ODBC ? I notice that there are some files > UV_SCHEMAS, > UV_TABLES, UV_USERS. The account Im trying to access is listed in > UV_SCHEMAS, but the file/table is not in UV_TABLES. Should it be ? Any > push in the right direction would be appreciated. > Thanks > Anthony Dzikiewicz > > > -- > ________________________________________________________ > Unsubscribe: mailto:[EMAIL PROTECTED] > or mailto:[EMAIL PROTECTED] > Moderator : mailto:[EMAIL PROTECTED] > Web-site : http://www.oliver.com/lists/u2 > > > -- > ________________________________________________________ > Unsubscribe: mailto:[EMAIL PROTECTED] > or mailto:[EMAIL PROTECTED] > Moderator : mailto:[EMAIL PROTECTED] > Web-site : http://www.oliver.com/lists/u2 > > > > > > > ************************************************************************ **** > ******* > > This transmission is intended for the named recipient only. It may contain > private and confidential information. If this has come to you in error you > must not act on anything disclosed in it, nor must you copy it, modify it, > disseminate it in any way, or show it to anyone. Please e-mail the sender to > inform us of the transmission error or telephone ECA International > immediately and delete the e-mail from your information system. > > Telephone numbers for ECA International offices are: Sydney +61 (0)2 9911 > 7799, Hong Kong + 852 2121 2388, London +44 (0)20 7351 5000 and New York +1 > 212 582 2333. > > ************************************************************************ **** > ******* > > > -- > ________________________________________________________ > Unsubscribe: mailto:[EMAIL PROTECTED] > or mailto:[EMAIL PROTECTED] > Moderator : mailto:[EMAIL PROTECTED] > Web-site : http://www.oliver.com/lists/u2 > > > > -- > ________________________________________________________ > Unsubscribe: mailto:[EMAIL PROTECTED] > or mailto:[EMAIL PROTECTED] > Moderator : mailto:[EMAIL PROTECTED] > Web-site : http://www.oliver.com/lists/u2 > > > > -- > ________________________________________________________ > Unsubscribe: mailto:[EMAIL PROTECTED] > or mailto:[EMAIL PROTECTED] > Moderator : mailto:[EMAIL PROTECTED] > Web-site : http://www.oliver.com/lists/u2 > > > > -- ________________________________________________________ Unsubscribe: mailto:[EMAIL PROTECTED] or mailto:[EMAIL PROTECTED] Moderator : mailto:[EMAIL PROTECTED] Web-site : http://www.oliver.com/lists/u2 Notice of Confidentiality: The information included and/or attached in this electronic mail transmission may contain confidential or privileged information and is intended for the addressee. Any unauthorized disclosure, reproduction, distribution or the taking of action in reliance on the contents of the information is prohibited. If you believe that you have received the message in error, please notify the sender by reply transmission and delete the message without copying or disclosing it. _______________________________________________ u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users _______________________________________________ u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
