Date:         Mon, 13 Sep 2010 21:12:20 -0400
Reply-To:     Nat Wooding <nathani@VERIZON.NET>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Nat Wooding <nathani@VERIZON.NET>
Subject:      Re: FileMaker to SAS via ODBC?
Comments: To: Roger A WIRT <Roger.A.Wirt@STATE.OR.US>
In-Reply-To:  <201009140013.o8DKPMU4031339@willow.cc.uga.edu>
Content-Type: text/plain; charset="US-ASCII"

Roger

Have you checked to see whether there is a SAS Tech Support document on ODBC
that may have some tips. This, of course, assumes that you have not already
been working from such a doc.

Nat Wooding

-----Original Message-----
From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of Roger A
WIRT
Sent: Monday, September 13, 2010 8:13 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: FileMaker to SAS via ODBC?

Thanks for your note.

Superficially, the libname function appears to be working in this
situation; in each of the tests that I mentioned SAS reported that a libref
was 'successfully assigned' to the remote system (with FileMaker user id &
password authentication).  We use the same desktop system and similar
SAS 'libname' programming to connect to a remote SQL Server system; once
SAS has assigned a libref in that context, voila: clicking an icon opens a
viewtable with data.  Not so with the ostensible FileMaker connection,
which displays icons but won't bring up any data.

I've wondered if the 'select from connection' approach would work, but
haven't been able to locate documentation of the necessary elements and
syntax to accomplish that with FileMaker (which has some distinctive
internal structural features of its own).  Guesses haven't yielded a
solution.

If the difficulties are due to driver incompatibilities, of course, no
amount of fiddling with the syntax would help.  Therefore it would be very
helpful to know if others have been able to get the connection to work for
non-trivial ODBC data transfers.

____________________________________
Is it any different if you use a connect to ODBC rather than a libname?  IE,
a 'select * from connection to odbc (... filemaker pro commands ...)' after
using 'connect to odbc (string)' ?  Some SQL2005 databases that I connect to
I can't use LIBNAME access because they're behind a schema behind a schema,
which SAS won't go two deep - but select * from connection to odbc (...)
works since I can use DBMS specific language in that select.

-Joe
... <snip> ...