Hi All

I have a question about connect ODBC from SAS. The table name in the ODBC
database include some space like "abc.subject date"

I use proc sql to pull out the data, but it seems SAS can not read a table
with name including space.

I don't have authority to change the ODBC, so does anyone have idea about it?

Thank you very much!

Jane

Can someone help me to fix this problem, or provide me other idea to pull
out data from ODBC?

Thanks

On 5/8/07, Jane <program.sas@gmail.com> wrote:
>
> Hi All
>
> I have a question about connect ODBC from SAS. The table name in the ODBC
> database include some space like "abc.subject date"
>
> I use proc sql to pull out the data, but it seems SAS can not read a table
> with name including space.
>
> I don't have authority to change the ODBC, so does anyone have idea about
> it?
>
> Thank you very much!
>
> Jane
>

Jane:
SAS has options that permit variations in dataset and column variable
names. For a single instance, it usually proves safer to treat a table
name as a name or string literal:

either ....SET or  ..... FROM abc.'subject date'n or 'abc.subject
date'n, depending on whether abc is a LIBNAME reference to a database
schema or part of the table name in the database schema. I suspect the
former. A SAS compiler treats a quoted string followed immediately by an
n as a special form of name.
S

-----Original Message-----
From: owner-sas-l@listserv.uga.edu [mailto:owner-sas-l@listserv.uga.edu]
On Behalf Of Jane
Sent: Tuesday, May 08, 2007 9:49 AM
To: SAS-L@LISTSERV.UGA.EDU
Cc: Jane
Subject: connect ODBC database from SAS


Hi All

I have a question about connect ODBC from SAS. The table name in the
ODBC database include some space like "abc.subject date"

I use proc sql to pull out the data, but it seems SAS can not read a
table with name including space.

I don't have authority to change the ODBC, so does anyone have idea
about it?

Thank you very much!

Jane

Thank you Sigurd. I still get some error message like this:

ERROR: CLI describe error: [Microsoft][ODBC SQL Server Driver][SQL
Server]Line 1: Incorrect
       syntax near 'subject date'. : [Microsoft][ODBC SQL Server Driver][SQL
       Server]Statement(s) could not be prepared.
When I use the totally same code to pull out another table with name without
space, everything is fine.

Do you have any idea about it?

Thanks

Jane

On 5/8/07, Sigurd Hermansen <HERMANS1@westat.com> wrote:
>
> Jane:
> SAS has options that permit variations in dataset and column variable
> names. For a single instance, it usually proves safer to treat a table
> name as a name or string literal:
>
> either ....SET or  ..... FROM abc.'subject date'n or 'abc.subject
> date'n, depending on whether abc is a LIBNAME reference to a database
> schema or part of the table name in the database schema. I suspect the
> former. A SAS compiler treats a quoted string followed immediately by an
> n as a special form of name.
> S
>
> -----Original Message-----
> From: owner-sas-l@listserv.uga.edu [mailto:owner-sas-l@listserv.uga.edu]
> On Behalf Of Jane
> Sent: Tuesday, May 08, 2007 9:49 AM
> To: SAS-L@LISTSERV.UGA.EDU
> Cc: Jane
> Subject: connect ODBC database from SAS
>
>
> Hi All
>
> I have a question about connect ODBC from SAS. The table name in the
> ODBC database include some space like "abc.subject date"
>
> I use proc sql to pull out the data, but it seems SAS can not read a
> table with name including space.
>
> I don't have authority to change the ODBC, so does anyone have idea
> about it?
>
> Thank you very much!
>
> Jane
>

BTW, here is my code:

proc sql;
  connect to odbc(dsn=Final_Report);
     create table work.test as select * from connection to odbc
    (select * from abc.'subject date'n);
  disconnect from odbc;
quit;




On 5/8/07, Jane <program.sas@gmail.com> wrote:
>
> Thank you Sigurd. I still get some error message like this:
>
> ERROR: CLI describe error: [Microsoft][ODBC SQL Server Driver][SQL
> Server]Line 1: Incorrect
>        syntax near 'subject date'. : [Microsoft][ODBC SQL Server
> Driver][SQL
>        Server]Statement(s) could not be prepared.
> When I use the totally same code to pull out another table with name
> without space, everything is fine.
>
> Do you have any idea about it?
>
> Thanks
>
> Jane
>
> On 5/8/07, Sigurd Hermansen <HERMANS1@westat.com> wrote:
> >
> > Jane:
> > SAS has options that permit variations in dataset and column variable
> > names. For a single instance, it usually proves safer to treat a table
> > name as a name or string literal:
> >
> > either ....SET or  ..... FROM abc.'subject date'n or ' abc.subject
> > date'n, depending on whether abc is a LIBNAME reference to a database
> > schema or part of the table name in the database schema. I suspect the
> > former. A SAS compiler treats a quoted string followed immediately by an
> >
> > n as a special form of name.
> > S
> >
> > -----Original Message-----
> > From: owner-sas-l@listserv.uga.edu [mailto:owner-sas-l@listserv.uga.edu
> > ]
> > On Behalf Of Jane
> > Sent: Tuesday, May 08, 2007 9:49 AM
> > To: SAS-L@LISTSERV.UGA.EDU
> > Cc: Jane
> > Subject: connect ODBC database from SAS
> >
> >
> > Hi All
> >
> > I have a question about connect ODBC from SAS. The table name in the
> > ODBC database include some space like "abc.subject date"
> >
> > I use proc sql to pull out the data, but it seems SAS can not read a
> > table with name including space.
> >
> > I don't have authority to change the ODBC, so does anyone have idea
> > about it?
> >
> > Thank you very much!
> >
> > Jane
> >
>
>

The code inside the parentheses must be written in SQL that is appropriate
for the specific ODBC data source that you are accessing.  Depending on what
data source that is (MS Access, MS Excel, or whatever) you might try
enclosing your problem table name in square brackets, single quotes, or
double quotes.  Leave off the "n" because that is a SAS-specific variation
that won't work inside the parentheses.

HTH,
s/KAM


----- Original Message -----
From: "Jane" <program.sas@gmail.com>
To: "Sigurd Hermansen" <HERMANS1@westat.com>
Cc: <SAS-L@LISTSERV.UGA.EDU>
Sent: Tuesday, May 08, 2007 09:50
Subject: Re: connect ODBC database from SAS


> BTW, here is my code:
>
> proc sql;
>  connect to odbc(dsn=Final_Report);
>     create table work.test as select * from connection to odbc
>    (select * from abc.'subject date'n);
>  disconnect from odbc;
> quit;
>
>
>
>
> On 5/8/07, Jane <program.sas@gmail.com> wrote:
>>
>> Thank you Sigurd. I still get some error message like this:
>>
>> ERROR: CLI describe error: [Microsoft][ODBC SQL Server Driver][SQL
>> Server]Line 1: Incorrect
>>        syntax near 'subject date'. : [Microsoft][ODBC SQL Server
>> Driver][SQL
>>        Server]Statement(s) could not be prepared.
>> When I use the totally same code to pull out another table with name
>> without space, everything is fine.
>>
>> Do you have any idea about it?
>>
>> Thanks
>>
>> Jane
>>
>> On 5/8/07, Sigurd Hermansen <HERMANS1@westat.com> wrote:
>> >
>> > Jane:
>> > SAS has options that permit variations in dataset and column variable
>> > names. For a single instance, it usually proves safer to treat a table
>> > name as a name or string literal:
>> >
>> > either ....SET or  ..... FROM abc.'subject date'n or ' abc.subject
>> > date'n, depending on whether abc is a LIBNAME reference to a database
>> > schema or part of the table name in the database schema. I suspect the
>> > former. A SAS compiler treats a quoted string followed immediately by
>> > an
>> >
>> > n as a special form of name.
>> > S
>> >
>> > -----Original Message-----
>> > From: owner-sas-l@listserv.uga.edu [mailto:owner-sas-l@listserv.uga.edu
>> > ]
>> > On Behalf Of Jane
>> > Sent: Tuesday, May 08, 2007 9:49 AM
>> > To: SAS-L@LISTSERV.UGA.EDU
>> > Cc: Jane
>> > Subject: connect ODBC database from SAS
>> >
>> >
>> > Hi All
>> >
>> > I have a question about connect ODBC from SAS. The table name in the
>> > ODBC database include some space like "abc.subject date"
>> >
>> > I use proc sql to pull out the data, but it seems SAS can not read a
>> > table with name including space.
>> >
>> > I don't have authority to change the ODBC, so does anyone have idea
>> > about it?
>> >
>> > Thank you very much!
>> >
>> > Jane
>> >
>>
>>
>
>

I'm not sure if SQL Server table names are case sensitive. You might
also want to try to type the table name in all UPPER CASE too. I
remember hearing about such an issue a while back.

Phil Rack
www.minequest.com


-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
Kevin Myers
Sent: Tuesday, May 08, 2007 11:01 AM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: connect ODBC database from SAS

The code inside the parentheses must be written in SQL that is
appropriate
for the specific ODBC data source that you are accessing.  Depending on
what
data source that is (MS Access, MS Excel, or whatever) you might try
enclosing your problem table name in square brackets, single quotes, or
double quotes.  Leave off the "n" because that is a SAS-specific
variation
that won't work inside the parentheses.

HTH,
s/KAM


----- Original Message -----
From: "Jane" <program.sas@gmail.com>
To: "Sigurd Hermansen" <HERMANS1@westat.com>
Cc: <SAS-L@LISTSERV.UGA.EDU>
Sent: Tuesday, May 08, 2007 09:50
Subject: Re: connect ODBC database from SAS


> BTW, here is my code:
>
> proc sql;
>  connect to odbc(dsn=Final_Report);
>     create table work.test as select * from connection to odbc
>    (select * from abc.'subject date'n);
>  disconnect from odbc;
> quit;
>
>
>
>
> On 5/8/07, Jane <program.sas@gmail.com> wrote:
>>
>> Thank you Sigurd. I still get some error message like this:
>>
>> ERROR: CLI describe error: [Microsoft][ODBC SQL Server Driver][SQL
>> Server]Line 1: Incorrect
>>        syntax near 'subject date'. : [Microsoft][ODBC SQL Server
>> Driver][SQL
>>        Server]Statement(s) could not be prepared.
>> When I use the totally same code to pull out another table with name
>> without space, everything is fine.
>>
>> Do you have any idea about it?
>>
>> Thanks
>>
>> Jane
>>
>> On 5/8/07, Sigurd Hermansen <HERMANS1@westat.com> wrote:
>> >
>> > Jane:
>> > SAS has options that permit variations in dataset and column
variable
>> > names. For a single instance, it usually proves safer to treat a
table
>> > name as a name or string literal:
>> >
>> > either ....SET or  ..... FROM abc.'subject date'n or ' abc.subject
>> > date'n, depending on whether abc is a LIBNAME reference to a
database
>> > schema or part of the table name in the database schema. I suspect
the
>> > former. A SAS compiler treats a quoted string followed immediately
by
>> > an
>> >
>> > n as a special form of name.
>> > S
>> >
>> > -----Original Message-----
>> > From: owner-sas-l@listserv.uga.edu
[mailto:owner-sas-l@listserv.uga.edu
>> > ]
>> > On Behalf Of Jane
>> > Sent: Tuesday, May 08, 2007 9:49 AM
>> > To: SAS-L@LISTSERV.UGA.EDU
>> > Cc: Jane
>> > Subject: connect ODBC database from SAS
>> >
>> >
>> > Hi All
>> >
>> > I have a question about connect ODBC from SAS. The table name in
the
>> > ODBC database include some space like "abc.subject date"
>> >
>> > I use proc sql to pull out the data, but it seems SAS can not read
a
>> > table with name including space.
>> >
>> > I don't have authority to change the ODBC, so does anyone have idea
>> > about it?
>> >
>> > Thank you very much!
>> >
>> > Jane
>> >
>>
>>
>
>

Sql server is not case sensitive but write the name of the tables go with the
PRESERVE_TAB_NAMES=YES option of the libref.

Jane, could you check something. the true name of the table is with 'abc.' or
without ?
On the MS sql query builder how do you write the same SELECT query ?

with the 'select * from connection to odbc' part, you can use a table without
the principle of the libref : if abc. is on the table, the quote start before
'abc.' word. otherwise, if you think that abc is the owner, you have to check
if your user can see the abc's tables. but in general with your proc SQL, you
don't need this prefix.


Cordialement/
Best regards,

Stephane COLAS


**************************
Societe Datametric

Notre site / Our site
http://www.datametric.fr
**************************


Selon Phil Rack <philrack@MINEQUEST.COM>:

> I'm not sure if SQL Server table names are case sensitive. You might
> also want to try to type the table name in all UPPER CASE too. I
> remember hearing about such an issue a while back.
>
> Phil Rack
> www.minequest.com
>
>
> -----Original Message-----
> From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
> Kevin Myers
> Sent: Tuesday, May 08, 2007 11:01 AM
> To: SAS-L@LISTSERV.UGA.EDU
> Subject: Re: connect ODBC database from SAS
>
> The code inside the parentheses must be written in SQL that is
> appropriate
> for the specific ODBC data source that you are accessing.  Depending on
> what
> data source that is (MS Access, MS Excel, or whatever) you might try
> enclosing your problem table name in square brackets, single quotes, or
> double quotes.  Leave off the "n" because that is a SAS-specific
> variation
> that won't work inside the parentheses.
>
> HTH,
> s/KAM
>
>
> ----- Original Message -----
> From: "Jane" <program.sas@gmail.com>
> To: "Sigurd Hermansen" <HERMANS1@westat.com>
> Cc: <SAS-L@LISTSERV.UGA.EDU>
> Sent: Tuesday, May 08, 2007 09:50
> Subject: Re: connect ODBC database from SAS
>
>
> > BTW, here is my code:
> >
> > proc sql;
> >  connect to odbc(dsn=Final_Report);
> >     create table work.test as select * from connection to odbc
> >    (select * from abc.'subject date'n);
> >  disconnect from odbc;
> > quit;
> >
> >
> >
> >
> > On 5/8/07, Jane <program.sas@gmail.com> wrote:
> >>
> >> Thank you Sigurd. I still get some error message like this:
> >>
> >> ERROR: CLI describe error: [Microsoft][ODBC SQL Server Driver][SQL
> >> Server]Line 1: Incorrect
> >>        syntax near 'subject date'. : [Microsoft][ODBC SQL Server
> >> Driver][SQL
> >>        Server]Statement(s) could not be prepared.
> >> When I use the totally same code to pull out another table with name
> >> without space, everything is fine.
> >>
> >> Do you have any idea about it?
> >>
> >> Thanks
> >>
> >> Jane
> >>
> >> On 5/8/07, Sigurd Hermansen <HERMANS1@westat.com> wrote:
> >> >
> >> > Jane:
> >> > SAS has options that permit variations in dataset and column
> variable
> >> > names. For a single instance, it usually proves safer to treat a
> table
> >> > name as a name or string literal:
> >> >
> >> > either ....SET or  ..... FROM abc.'subject date'n or ' abc.subject
> >> > date'n, depending on whether abc is a LIBNAME reference to a
> database
> >> > schema or part of the table name in the database schema. I suspect
> the
> >> > former. A SAS compiler treats a quoted string followed immediately
> by
> >> > an
> >> >
> >> > n as a special form of name.
> >> > S
> >> >
> >> > -----Original Message-----
> >> > From: owner-sas-l@listserv.uga.edu
> [mailto:owner-sas-l@listserv.uga.edu
> >> > ]
> >> > On Behalf Of Jane
> >> > Sent: Tuesday, May 08, 2007 9:49 AM
> >> > To: SAS-L@LISTSERV.UGA.EDU
> >> > Cc: Jane
> >> > Subject: connect ODBC database from SAS
> >> >
> >> >
> >> > Hi All
> >> >
> >> > I have a question about connect ODBC from SAS. The table name in
> the
> >> > ODBC database include some space like "abc.subject date"
> >> >
> >> > I use proc sql to pull out the data, but it seems SAS can not read
> a
> >> > table with name including space.
> >> >
> >> > I don't have authority to change the ODBC, so does anyone have idea
> >> > about it?
> >> >
> >> > Thank you very much!
> >> >
> >> > Jane
> >> >
> >>
> >>
> >
> >
>

Jane:
You are passing the query through directly to the DBMS. In that case,
anything that the SAS SQL compiler doesn't block and the DBMS will
accept as a query will work OK. The query will execute as if it were
executed in something like MS SQL Server Enterprise Guide or MS Access
query builder. The error message is being relayed from the DBMS to SAS.
SAS isn't objecting to the name literal, as it shouldn't, but the DBMS
is, which seems likely and normal.=20
=20
The DBMS may require square brackets, for instance abc.[subject date],
around the table name. Since I don't know the DBMS to which you are
connecting, I can only infer that the DBMS compiler doesn't recognize a
SAS name literal. It doesn't provide any clues about what the DBMS
expects to see. I'd try enclosing the table name in square brackets as a
first step. Let us know if the DBMS returns another error message, or
what DBMS you are trying to access.
S
=20

        -----Original Message-----
        From: Jane [mailto:program.sas@gmail.com]=20
        Sent: Tuesday, May 08, 2007 10:51 AM
        To: Sigurd Hermansen
        Cc: SAS-L@listserv.uga.edu
        Subject: Re: connect ODBC database from SAS
=09
=09
        BTW, here is my code:
=09
        proc sql;
          connect to odbc(dsn=3DFinal_Report);
             create table work.test as select * from connection to odbc
            (select * from abc.'subject date'n);
          disconnect from odbc;=20
        quit;
=09
=09
=09
=09
=09
        On 5/8/07, Jane <program.sas@gmail.com> wrote:=20

                Thank you Sigurd. I still get some error message like
this:
        =09
                ERROR: CLI describe error: [Microsoft][ODBC SQL Server
Driver][SQL Server]Line 1: Incorrect
                       syntax near 'subject date'. : [Microsoft][ODBC
SQL Server Driver][SQL=20
                       Server]Statement(s) could not be prepared.
                When I use the totally same code to pull out another
table with name without space, everything is fine.
        =09
                Do you have any idea about it?
        =09
                Thanks
        =09
                Jane=20
        =09
        =09
        =09
                On 5/8/07, Sigurd Hermansen < HERMANS1@westat.com
<mailto:HERMANS1@westat.com> > wrote:=20

                        Jane:
                        SAS has options that permit variations in
dataset and column variable
                        names. For a single instance, it usually proves
safer to treat a table
                        name as a name or string literal:
                =09
                        either ....SET or  ..... FROM abc.'subject
date'n or ' abc.subject
                        date'n, depending on whether abc is a LIBNAME
reference to a database
                        schema or part of the table name in the database
schema. I suspect the
                        former. A SAS compiler treats a quoted string
followed immediately by an=20
                        n as a special form of name.
                        S
                =09
                        -----Original Message-----
                        From: owner-sas-l@listserv.uga.edu
[mailto:owner-sas-l@listserv.uga.edu ]
                        On Behalf Of Jane
                        Sent: Tuesday, May 08, 2007 9:49 AM
                        To: SAS-L@LISTSERV.UGA.EDU
                        Cc: Jane=20
                        Subject: connect ODBC database from SAS
                =09
                =09
                        Hi All
                =09
                        I have a question about connect ODBC from SAS.
The table name in the=20
                        ODBC database include some space like
"abc.subject date"
                =09
                        I use proc sql to pull out the data, but it
seems SAS can not read a
                        table with name including space.
                =09
                        I don't have authority to change the ODBC, so
does anyone have idea=20
                        about it?
                =09
                        Thank you very much!
                =09
                        Jane
                =09

Jane,

could you test this if the abc was not the owner ?

Change the owner DBO if it's not the good for you.

Proc SQL;
Connect to ODBC as dblink (dsn=Final_Report);
create table work.test2 as select * from connection to dblink
(select * from [dbo].[abc.subject date]);
disconnect from dblink;
quit;


Stephane.


Selon Stephane COLAS <scolas@datametric.fr>:

> Sql server is not case sensitive but write the name of the tables go with the
> PRESERVE_TAB_NAMES=YES option of the libref.
>
> Jane, could you check something. the true name of the table is with 'abc.' or
> without ?
> On the MS sql query builder how do you write the same SELECT query ?
>
> with the 'select * from connection to odbc' part, you can use a table without
> the principle of the libref : if abc. is on the table, the quote start before
> 'abc.' word. otherwise, if you think that abc is the owner, you have to check
> if your user can see the abc's tables. but in general with your proc SQL, you
> don't need this prefix.
>
>
> Cordialement/
> Best regards,
>
> Stephane COLAS
>
>
> **************************
> Societe Datametric
>
> Notre site / Our site
> http://www.datametric.fr
> **************************
>
>
> Selon Phil Rack <philrack@MINEQUEST.COM>:
>
> > I'm not sure if SQL Server table names are case sensitive. You might
> > also want to try to type the table name in all UPPER CASE too. I
> > remember hearing about such an issue a while back.
> >
> > Phil Rack
> > www.minequest.com
> >
> >
> > -----Original Message-----
> > From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
> > Kevin Myers
> > Sent: Tuesday, May 08, 2007 11:01 AM
> > To: SAS-L@LISTSERV.UGA.EDU
> > Subject: Re: connect ODBC database from SAS
> >
> > The code inside the parentheses must be written in SQL that is
> > appropriate
> > for the specific ODBC data source that you are accessing.  Depending on
> > what
> > data source that is (MS Access, MS Excel, or whatever) you might try
> > enclosing your problem table name in square brackets, single quotes, or
> > double quotes.  Leave off the "n" because that is a SAS-specific
> > variation
> > that won't work inside the parentheses.
> >
> > HTH,
> > s/KAM
> >
> >
> > ----- Original Message -----
> > From: "Jane" <program.sas@gmail.com>
> > To: "Sigurd Hermansen" <HERMANS1@westat.com>
> > Cc: <SAS-L@LISTSERV.UGA.EDU>
> > Sent: Tuesday, May 08, 2007 09:50
> > Subject: Re: connect ODBC database from SAS
> >
> >
> > > BTW, here is my code:
> > >
> > > proc sql;
> > >  connect to odbc(dsn=Final_Report);
> > >     create table work.test as select * from connection to odbc
> > >    (select * from abc.'subject date'n);
> > >  disconnect from odbc;
> > > quit;
> > >
> > >
> > >
> > >
> > > On 5/8/07, Jane <program.sas@gmail.com> wrote:
> > >>
> > >> Thank you Sigurd. I still get some error message like this:
> > >>
> > >> ERROR: CLI describe error: [Microsoft][ODBC SQL Server Driver][SQL
> > >> Server]Line 1: Incorrect
> > >>        syntax near 'subject date'. : [Microsoft][ODBC SQL Server
> > >> Driver][SQL
> > >>        Server]Statement(s) could not be prepared.
> > >> When I use the totally same code to pull out another table with name
> > >> without space, everything is fine.
> > >>
> > >> Do you have any idea about it?
> > >>
> > >> Thanks
> > >>
> > >> Jane
> > >>
> > >> On 5/8/07, Sigurd Hermansen <HERMANS1@westat.com> wrote:
> > >> >
> > >> > Jane:
> > >> > SAS has options that permit variations in dataset and column
> > variable
> > >> > names. For a single instance, it usually proves safer to treat a
> > table
> > >> > name as a name or string literal:
> > >> >
> > >> > either ....SET or  ..... FROM abc.'subject date'n or ' abc.subject
> > >> > date'n, depending on whether abc is a LIBNAME reference to a
> > database
> > >> > schema or part of the table name in the database schema. I suspect
> > the
> > >> > former. A SAS compiler treats a quoted string followed immediately
> > by
> > >> > an
> > >> >
> > >> > n as a special form of name.
> > >> > S
> > >> >
> > >> > -----Original Message-----
> > >> > From: owner-sas-l@listserv.uga.edu
> > [mailto:owner-sas-l@listserv.uga.edu
> > >> > ]
> > >> > On Behalf Of Jane
> > >> > Sent: Tuesday, May 08, 2007 9:49 AM
> > >> > To: SAS-L@LISTSERV.UGA.EDU
> > >> > Cc: Jane
> > >> > Subject: connect ODBC database from SAS
> > >> >
> > >> >
> > >> > Hi All
> > >> >
> > >> > I have a question about connect ODBC from SAS. The table name in
> > the
> > >> > ODBC database include some space like "abc.subject date"
> > >> >
> > >> > I use proc sql to pull out the data, but it seems SAS can not read
> > a
> > >> > table with name including space.
> > >> >
> > >> > I don't have authority to change the ODBC, so does anyone have idea
> > >> > about it?
> > >> >
> > >> > Thank you very much!
> > >> >
> > >> > Jane
> > >> >
> > >>
> > >>
> > >
> > >
> >
>