My FM links to SQL Server 2000 are working fine, Mac and Windows,
read and write.
My FM links to SQL Server 2005 are the problem - specifically writes
from Windows.
I can link to the tables I need from both Mac and Windows
workstations. My Macs are using the Actual Technologies SQL drivers,
and the Windows stations use the Microsoft supplied SQL drivers. The
Mac stations write to the SQL 2005 tables with no problem. The
Windows stations get an error when they try to write: "ODBC Error:
[Microsoft][ODBC SQL Server Driver]Invalid precision value".
Any suggestions?
-----------------------------------------
Andrew Kappy
On Dec 16, 2008, at 9:54 AM, Beverly Voth wrote:
There are these help topics (fmp9) under the category "Sharing data":
* Using ODBC and JDBC with FileMaker Pro
* Accessing external data sources
Also, you can search the knowledge base on the FMI site for "ODBC"
and "ESS"
(two different searches).
To recap FileMaker and ODBC (these all require drivers):
1) SHARE FMP as a data source (other ODBC can see FMP)
2) Connect to SQL data source with FMP through ODBC and using
IMPORT and
Execute SQL script steps (uses real SQL calls!)
3) Connect to External SQL Source ("ESS") with FMP through ODBC
(does
not require using SQL calls, you can search, add, edit, delete --
if you
have these permissions on the SQL server). SQL "Tables" appear very
much
like FMP tables, you just can't change the schema (field/column
definitions)
of the SQL tables.
More details, of course in the all the documentation.
HTH,
Beverly
On 12/16/08 6:28 AM, "Rowland & Wilma Carson" <[email protected]>
wrote in
whole or in part:
At 2008-12-15 16:08 -0500 Beverly Voth 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 - I think it's time for me to duck below the parapet again! I
hadn't noticed the context of the remarks and apologise if I caused
confusion to anyone by my too-hasty posting.
Fools rush in dept: I didn't know what ESS stands for and never seen
it before until just now when I now found one mention in the appendix
of Ray Cologon's book. Sounds like what I am doing, but I note that
he says it involves a DSN on the host; I have been using a DSN on the
clients so I guess I am doing something different.
regards
Rowland
