RE: CA 32-bit ODBC and Excel -- MIDRANGE-L

Gary, 
You will know if you read this. It's really simple. Some of  ODBC
clients determine the name of the remote database by issuing a request
type API to the server. The server responds with the proper name to be
used in all subsequent ODBC requests. I forget the details, but the name
of the database table has several qualifiers, the first of which is the
database name. If you have not named the AS/400 RDBMS (ADDRDBDIRE), the
name returned is *N. PC recognises the name as valid and attempts to use
*N.collection.table (or something of that sort) as the table name.
Naturally, this format does not adhere to SQL standards, and therefore
you get the error message. Once you define the AS/400 database,
everything works fine.

Lo 

> -----Original Message-----
> From: Gary Lehman [SMTP:Gary_Lehman@mail.mchcp.org]
> Sent: 29 June 1998 18:25
> To:   'midrange-l@midrange.com'
> Subject:      RE: CA 32-bit ODBC and Excel
> 
> I tried this again and now it works!!!  This is really strange, but
> the only
> thing I have done is the ADDRDBDIRE command, but I tried that the
> other day
> and nothing worked.  I wonder if something with the subsystems
> restarting
> had anything to do with it.  Guess I'll never know. :-)
> 
> Gary Lehman
> Programmer Analyst
> Missouri Consolidated Health Care Plan
> 
>               -----Original Message-----
>               From:   Vernon Hamberg [mailto:hambergv@goldengate.net]
>               Sent:   Friday, June 26, 1998 6:30 PM
>               To:     MIDRANGE-L@midrange.com
>               Cc:     Gary_Lehman@mail.mchcp.org
>               Subject:        Re: CA 32-bit ODBC and Excel
> 
>               Gary
> 
>               At 11:43 AM 6/26/1998 -0500, you wrote:
>               >Hello,
>               >
>               >I was wondering if anyone knew anything about the
> Client
> Access 32 bit ODBC
>               >driver.  I can get it to work in Access but when I try
> to
> use it in Excel
>               >I'm getting an SQL0104 error - Token * was not valid.
> Valid
> tokens:
>               ><IDENTIFIER>.  The help just says there is something
> wrong
> with the driver,
>               >but it's the most up to date driver that I know of.
> Does
> anyone have any
>               >suggestions?
> 
>               There are some known problems with MS Query. You can
> find
> out more by going
>               to <http://www.as400.ibm.com/clientaccess> and following
> the
> link to
>               information APARs. There are a number of them that deal
> with
> ODBC.
> 
>               HTH
> 
>               Vernon Hamberg
>               Systems Software Programmer
>               Old Republic National Title Insurance Company
>               400 Second Avenue South
>               Minneapolis, MN  55401-2499
>               (612) 371-1111 x480
>               
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---