Developer License Key Issue

[Computer Geek]

I posted sometime in the past asking if anyone had problems opening another fm file by calling it from within a script. I have seen other posts on the matter, and forgive me if someone already posted solution, but I got a response from Filemaker Inc today on the problem.

The general problem is that when you open another hosted file via a script when you only own 1 developer licence key, it displays and error message that you exceeded your 1 user license key. This is very annoying, as you are not exceeding your key.

There is a known issue (at least to the FM techs) that if the file you are calling is not called exactly the first hosted file was opened, it will cause the error. Therefore, the file references must be identical to the open remote command. In my case, when I opened the file via open remote, it went to 10.10.1.250/menu. My file reference for the second file was admserver.mycompanyname.com/file2. Admserver.mycompanyname.com resolves to 10.10.1.250. Developer sees this as a violation of the license key. The work around was changing the first file's opening path to admserver.mycompanyname.com.

Another tidbit that I garnered from them is that if you have two licensed servers and try opening a file on each server, it will bomb too if you only have one license. Although I don't have that problem, I thought I would mention it.

[QuinTech]

Hmmm... i'm not sure i agree that this is an "issue." Seems more like a matter of maintaining programming consistency. Why do you call one file through a pure IP address but another on the same machine by DNS name?

Jerry

[Computer Geek]

I disagree that it is not an issue. The developer license is for one computer. A user should be able to use a solution on 1 computer without it bombing, whether or not the programming is consistant or inconsistant. In any case, FileMaker recognizes it as a known issue that should be corrected in the next updater release.

[laker_42]

I am running into this same issue. I have been running around in circles with tech support for the last 3 days. I can't get the techs to acknowledge that it is a known issue. They keep insisting that it is a problem with our server or our databases.

You mentioned that changing the first files opening path. Where do you do this at?

Thanks!

John

[Computer Geek]

John,

From point A to point Z, you must call/open each file on your server in the exact same way. If in the open remote, the host name has to be the same as all the calls from any file references from within your solution.

For example:

In open remote: host = fms.yourdomainname.com/filename

In your file references: fmnet:/192.168.1.1/filename

If yourdomainname.com points to 192.168.1.1, one would think that both would open correctly. However, with the issue in Developer, the it sees them as two separate copies of developer, causing a licensing violation. Really, there is no violation of the license as the license is for one computer not one server.

The solution is to either change the Open Remote host to the IP address or all the file references in all your files to the yourdomainname.com. FileMaker told me that they are working on the fix and it should be out in the next updater.

By the way, if you have a volume license, this becomes moot, as there is not a license check when you open files on the server.

HTH.