RE: Enabling ODBC for non-SQL file
I hope you corrected the wiki if you found any mistakes :-) It's basically a write-up of what I did (and still do when I need to validate files). The verbose HS.UPDATE.FILEINFO doesn't catch problems with individual files - it lets you know if it's fallen over and left a load of files unprocessed - that caught us badly :-( I'm guessing from the error that you might have a load of spaces or other invisible crud in field 3! You could try deleting it and typing it in again. I think I've known that work ... Step one - make sure all the i-types have been compiled. step two - if that doesn't work, delete all the itypes and see if the file appears okay step three - if that doesn't work, scream and shout! Otherwise, add the itypes back one by one, making sure they're compiled, that you can list them from tcl, etc etc. I've never used just plain "varchar", so I haven't direct experience of what you've done. And you might try removing the itypes just from @SELECT rather than from the DICT. That might work, and might make eliminating the problem easier. The other thing - can you export the problem file directly? I think we've had problems where the trans'd (or whatever) file had the problem there. When you get odbc problems, they're a sod, aren't they :-) I think you're going to have to just logically eliminate every possibility one by one. Use this email list copiously to make sure you understand what you're doing, then write the problem up and add it to the wiki :-) Cheers, Wol -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Hester Sent: 17 February 2004 21:09 To: U2 Users Discussion List Subject: Re: Enabling ODBC for non-SQL file Anthony Youngman wrote: > Did you run HS.UPDATE.FILEINFO? > > Have you put the correct SQL type definitions in fields 8? > > Did HS.UPDATE.FILEINFO actually work correctly! THAT'S A BIGGIE! > > I've shoved a little article on pickwiki you might want to look at - > multivaluedatabases>universe>odbcaccess > > Cheers, > Wol Thanks for pointing me to the pickwiki. That was a lot easier to follow than the UV documentation. I made sure the correct SQL types were in attr. 8 of all the dict items. I had previously cleared the entire dict and put in only the things I needed (I copied the live file to a separate ODBC-only account), so I only have a handful to worry about. I also manually added the file to HS_FILE_ACCESS. I used the verbose version of HS.UPDATE.FILEINFO from the wicki and there were no complaints about this particular file. Still can't get this file to be seen though. HS.SCRUB does give an error message on all the I-type dict items and I'm not sure exactly what it's telling me. I get this message: CUST.CITY was analyzed using VARCHAR(254) for a data type * Invalid conversion code ' '. And here's the I-type: 0001: I 0002: TRANS(CR,@ID[8,8],21,"X") 0003: 0004: CITY 0005: 20L 0006: S 0007: 0008: VARCHAR The I-type is referencing a file that's a Q-pointer to a non-SQL file in another account. All the other I-types it complains about point to the same file. The only other potential problem I can think of is since I'm using a stripped down version of the actual dict, there are attributes in the data portion that now have no corresponding dict entry. Could this be a problem? Thanks, John -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users *** 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. *** -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
Re: Enabling ODBC for non-SQL file
Nevermind. Appears the problem is on the client side. More specifically Excel in Office 2000. I was using Excel on a Windows server 2003 box running terminal services and Citrix. I decided to try OpenOffice on my XP Pro desktop, where I have no MS Office installed, and so far it appears to work perfectly. Every file in the account shows up now. -John -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
Re: Enabling ODBC for non-SQL file
Anthony Youngman wrote: Did you run HS.UPDATE.FILEINFO? Have you put the correct SQL type definitions in fields 8? Did HS.UPDATE.FILEINFO actually work correctly! THAT'S A BIGGIE! I've shoved a little article on pickwiki you might want to look at - multivaluedatabases>universe>odbcaccess Cheers, Wol Thanks for pointing me to the pickwiki. That was a lot easier to follow than the UV documentation. I made sure the correct SQL types were in attr. 8 of all the dict items. I had previously cleared the entire dict and put in only the things I needed (I copied the live file to a separate ODBC-only account), so I only have a handful to worry about. I also manually added the file to HS_FILE_ACCESS. I used the verbose version of HS.UPDATE.FILEINFO from the wicki and there were no complaints about this particular file. Still can't get this file to be seen though. HS.SCRUB does give an error message on all the I-type dict items and I'm not sure exactly what it's telling me. I get this message: CUST.CITY was analyzed using VARCHAR(254) for a data type * Invalid conversion code ' '. And here's the I-type: 0001: I 0002: TRANS(CR,@ID[8,8],21,"X") 0003: 0004: CITY 0005: 20L 0006: S 0007: 0008: VARCHAR The I-type is referencing a file that's a Q-pointer to a non-SQL file in another account. All the other I-types it complains about point to the same file. The only other potential problem I can think of is since I'm using a stripped down version of the actual dict, there are attributes in the data portion that now have no corresponding dict entry. Could this be a problem? Thanks, John -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
RE: Enabling ODBC for non-SQL file
Did you run HS.UPDATE.FILEINFO? Have you put the correct SQL type definitions in fields 8? Did HS.UPDATE.FILEINFO actually work correctly! THAT'S A BIGGIE! I've shoved a little article on pickwiki you might want to look at - multivaluedatabases>universe>odbcaccess Cheers, Wol -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Hester Sent: 17 February 2004 01:11 To: U2 Users Discussion List Subject: Re: Enabling ODBC for non-SQL file 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 *** 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. *** -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
Re: Enabling ODBC for non-SQL file
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
RE: Enabling ODBC for non-SQL file
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 -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
