Hi, Thanks for the suggestions. Here's what I've found.
I've got the Unidata ODBC driver version number 3.01.04.7013, so it's a little earlier than you mentioned. I also tried setting up a .dsn file as you mentioned, and that didn't seem to work either. Is there a way to download a 'Service Pack' for this, or do I need to obtain an upgrade CD from our VAR? Any other ideas? Thanks, Dave -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Tuesday, February 17, 2004 12:07 PM To: [EMAIL PROTECTED] Subject: RE: Unidata ODBC initial setup error - Run out of ideas!!! What version of the driver do you have? I had similar issues with an old driver, I now have 3.01.04.7036 which seems to be working OK, I think it is from the 6.0B Client CD. Although at one time it would work from Access but not Excel?!?! I'm not sure what's changed (perhaps some MS updates). The other key thing is the UCI.CONFIG file. If you treat *everything* in this file as case-sensitive things seem to work a lot easier. IBM also sent me this tech tip when I had this problem: Can you check if this TechTip helps solve the problem. It seems to be an issue with Microsoft Excel. With the upgrade to Microsoft's ODBC Administrator 3.0 there is a change in the use of data source definition with the 32 bit data source. Use of Office 97 or upgrading to Visual Basic 5.0 automatically upgades the 32 bit ODBC Administrator to 3.0 from the previous 2.0 or 2.5 versions. Unfortunately, there is a confusing error that is generated from Microsoft Query/Excel when you try to get external data : Key value must not contain any of the following characters: []{}(),;?*=!@ After you create the data source as a User DSN, you need to create a file.dsn text file. In Windows 95/Windows NT in the directory path /Program Files/Common Files/ODBC/Data Sources. copy an existing .dsn file (or with any editor create a new one). The file contains the following: [ODBC] DSN=sourcename (where sourcename is the name of your data source). If your User DSN entry data source = TSTODBC, then create a file called TSTODBC.dsn or any name you choose with the .dsn suffix. The text is as above: [ODBC] DSN=TSTODBC hth -- Colin Alfke Calgary, Alberta Canada "Just because something isn't broken doesn't mean that you can't fix it" Stu Pickles >-----Original Message----- >From: Dave Tabor [mailto:[EMAIL PROTECTED] >Sent: Tuesday, February 17, 2004 9:52 AM >To: U2 Users Discussion List >Subject: Unidata ODBC initial setup error - Run out of ideas!!! > > >Hi, > >Although I'm an old hand at Unidata and UniBasic, I'm a newbie >to ODBC. > >I am trying to set up an ODBC link to my Unidata 6.0 database, >using the Unidata ODBC driver that came with 6.0, to use in a >VB.net application I'm writing. All seems to be set properly, >but if I try to do a test of my connection by going to Excel >and doing Data/Get External Data/New Database Query from the >menu, I always get an error saying "Non-numeric found when >numeric required." > >Here's what I've done to this point: > >I've modified the uni.config file on the AIX 5.1.server. > >I'm creating a schema for the file using the VSG program >included with Unidata 6.0. I'm picking the file from the list >of files, assigning ALL permissions to PUBLIC. I'm creating a >view and schema using all fields (I have tried with only the >text fields). > >My test file (1NF format) has fields of Name (25L Text), Town >(25L Text) & Code (8R Number Conv=MR0). My @ID is a number (3 >records: 1, 2 & 3). Valid data in each field. I've tried the >@ID field with and without a Conv of MR0. With the MR0, VSG >calls it an integer. Without the MR0, VSG calls it a VARCHAR. > I get no errors while creating the schema in VSG, and I do >see all the 'D' type dictionary fields in VSG, so it appears >that it's not a network related error. > >I'm creating a link to the database in Windows XP Pro (and >Win2000 Pro) - Administration Tools - Data Sources. There >isn't much to configure here, and I think it's all set up ok. > >I'm trying to use Excel (have tried Access, too), to see if I >can pull in the data, and I always get the message >"Non-numeric found when numeric required". > >Any ideas? > >Thanks, >- Dave >-- >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 -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
