This sounds like the THIRD method working with FMP and ODBC. This sounds like you need to publish FMP and share it, so that other ODBC sources can see it. Please read the "ODBC and JDBC Guide", available on the FMI site, if you don't have it. Remember that FMS Advanced 9 is required to share FMP as an ODBC data source.
The SequeLink drivers should be available on your install CD. Beverly On 12/15/08 4:25 PM, "Steve Roethel" <[email protected]> wrote in whole or in part: > Hello: > > I have a related issue regarding ODBC drivers / file config. > > I have a client that is consolidating their emergency dispatching to a local > E911 center and they have asked me for the ODBC driver so they can read my > solution containing addresses and commercial business info. They would like > to and plug the info into their existing system. > > I can get system info if needed. > > Any suggestions appreciated! > > Steve > OSX 10.4.11 - FM9 > Win Server2003 FMS8 > > > > > On 12/15/08 4:08 PM, "Beverly Voth" <[email protected]> wrote: > >> Rowland, Steve is referring to using ODBC (with IMPORT[] or Execute SQL[] >> script steps). The "ESS" method (which may be what you are using) *is* a >> direct connection to the live SQL source. These are two different things and >> I thought Steve explained that. >> >> Beverly >> >> On 12/15/08 3:40 PM, "Rowland & Wilma Carson" <[email protected]> wrote in >> whole or in part: >> >>> At 2008-12-13 15:53 -0800 Steve B. Gerow wrote: >>> >>>> FileMaker can connect to any ODBC datasource for which there is a >>>> driver availiable. You can import data from the ODBC data source >>>> into FileMaker but cannot modify* the data in the source itself with >>>> ODBC >>> >>> Steve - having just implemented a solution which uses FMP front-ends >>> on users' own machines to connect via ODBC to a central MySQL server, >>> I feel the need to question what you _seem_ to be saying. Forgive me >>> if I am not understanding you correctly. >>> >>> It's correct that FMP cannot alter the _structure_ of a SQL served >>> database accessed through ODBC, but the FMP users can certainly >>> modify the _data_ held therein, and my solution depends upon it. >>> >>> The average end-user will not want to tinker with the database >>> structure, so it's not an issue in my situation. >>> >>> There are some slight differences between handling tables accessed >>> through ODBC and native FMP tables, but for the most part (once set >>> up using MySQL Admin or phpMyAdmin) they can be treated just like >>> native FMP tables. You can add FMP-native calculated and summary >>> fields to ODBC-based tables. >>> >>> It seems much easier to find hosting services for MySQL than for FMP; >>> I'd expect this FMP9 feature to be a popular reason for upgrading to >>> 9. >>> >>> Incidentally, I find that the Actual ODBC Mac drivers for MS Access >>> only allow _import_ of Access data, which sounds a bit like what you >>> seem to be saying about the SQL ODBC drivers. Of course, that makes >>> sense anyway as there is no MS Access engine on the Mac so if the >>> data file is held on the Mac, it _has_ to be read-only. >>> >>> regards >>> >>> Rowland >>
