Runtime solutions cannot connect to external FMP databases. They are not FMP networkable.
You should view the runtime product specifications for all the ways a runtime is different from the regular FMP.
Thanks for the quick reply. It seems there's a bit more than just the specs. The HELP section addresses it in a very misleading way...
Verifying FileMaker data sources-(From Runtime Section of FMPAdv. HELP)
In addition, if you have been preparing multiple files in separate folders, you need to verify FileMaker data source references.....
...The Manage External Data Sources dialog box lists the data sources in the current database. Be sure that for each FileMaker data source, there is a reference in the File Path that is to the filename only, without any folders. The data source will look like this: file:MyFile.fmp12. See Connecting to data sources for more information.
Technically it is correct.
An external reference can be either a local file, as is the case for a runtime, or a network shared file. The "file:/" reference refers to a file that is 'local' in relationship to the current file. For a file on the hard drive that means only another file located on the same computer, normally the same hard drive, but not required to be in the same folder as the current file. Thus the reference to the folder heirarchy. For a network shared file it means only a file shared on the same FMS (or FMP host) as the current file.
A Runtime cannot use the "fmnet:/IP/filename" file reference.
I am reviewing Appendix A right now, and explicitly it states this as a function that's not avlbl.
What about FM Go?...'Go-ing' to look now.
OK, I just confirmed, that all is cool in FMGo. It's open remote is valid for iOS in scripts.