802 is not ODBC error, check the access of file to import
or don't you use table from another file to import or ESS ?
I believe you are correct when you say 802 is not an ODBC error however the rest of the script processes without error according to the server logs. The error is on the IMPORT RECORDS step only. I suspect that it is an access problem but the script processes correctly when run on the server itself using the regular Filemaker Pro client software.
I don't care for ESS in my particular application because my users have to perform searches on some of the data and ESS requires the use of Oracle syntax when searching. For instance searches become case sensitive and the percentage sign is required as wildcard. This makes searching very different from native Filemaker and I can imagine the users balking at it.
"For instance searches become case sensitive and the percentage sign is required as wildcard."
I can use the "*" as a wildcard on my ESS-Oracle connections and it works just fine. You can solve the case-sensitive issue using a Custom Menu that replaces the Perform Find command in Find Mode.
Just out of curiosity, though, do you have both the 32-bit and 64-bit drivers installed? I've found that this is necessary in version 12 and later because it's a mixed environment (client vs. Server).
Is it mixed on the server? I know the database itself is 64 bit but isn't the scripting engine 32 bit?
Yes, it's mixed on the server.
IT WORKS! Mike, you're the man! I'd award you 1,000 points for this one if I could.
FM Server 13 needs both the 32 bit and the 64 bit Oracle ODBC drivers. The FM articles talk about the two but they don't come right out and say that you MUST have both installed on the server and I assume that both DSN's must be named identically.
So for for future reference here's what I did in this exact order:
Installed the 64 bit Oracle client in a folder named c:\Oracle64
Installed the 32 bit Oracle client in a folder named c:\Oracle32
Copied the TNSnames.ora file into the ADMIN folder of each install.
Configured the 32 bit DSN.
Configured the 64 bit DSN. (BTW, the 32 bit DSN can be seen in the 64 bit window but can't be edited or deleted)
One more thing. To get the ODBC connection to work on my 64 bit Windows 8.1 PC I had to install Filemaker in a folder named "c:\Program Files Special" and configure the executible to "Run As Administrator"
Thanks again Mike, you led me in the right direction!
You're welcome. Glad you got it working.