It is compatible.
Right now I have FM10 Pro Adv and FM11 Pro Adv installed on my computer (Windows XP). In the Open Remote dialog box, both FM 10 and FM11 see the server. However, only FM10 shows databases in the right pane. If I specify the file in the file name box I get the message:
The file "yourfile.fp7" could not be opened. Either the host is not available, or the file is not available on that host.
Anyone else able to connect?
I'm connected right now with Filemaker 11 adv as my client and server 10 as the host for several files. Just don't try to open the same file from both Filemaker 10 and 11 at the same time. I doubt that'll work.
Nope, that's not it. Guess I'll call tech support. I'll let you guys know how it goes.
I did more hunting and found this little gem (FILEMAKER, Please Fix THIS BUG!!!!!!!!!):
It is in fact an SSL issue. I fixed the problem by replacing the server.pem SSL certificate file with one from a working system. While this is a full working solution, it comes with a caveat. This will allow you to leave SSL encryption enabled, but having the same cert on multiple client machines is generally a bad idea.
-Replace server.pem at the "Program Files > FileMaker > FileMaker <ver>" directory. <---- I didn't even have this file!!!!
-Replace server.pem at the "Applications > FileMaker <ver> > FileMaker <ver>.app > Contents > MacOS" directory. Note: A *.app (application) package can be accessed by right/control clicking on it and choosing "Show Package Contents".
The bug is caused because the FileMaker installer fails to create a valid certificate file on install. Each cert file contains "not before" and "not after" dates to define the scope of the certificate. The "not before" date is the date of the install. The "not after" date is 863913600 seconds (9,999 days) after the install date. If you add 863913600 seconds to any date after September 22th, 2008, the date is incorrectly interpreted by the installer as a date on or after Jan 1st, 1970. This makes the cert unusable because the "not after" date is in 1970 and 2008 is definitely after 1970. This affects multiple versions of FileMaker. Seems like the cause is not a code change or update. Time just had to pass to make this one happen.
The best solution to the problem is to do a reinstall of the application while having your computer's clock set to a date before September 22th, 2008, apply all updates and set the date back to today. The cert that's created should be valid.
We have tried to change the date manually, but the encrypted portion of the certificate relies on the original date set. It did not work.
Loosely related material:
http://en.wikipedia.org/wiki/Year_2038_proble m<!-- POLLS --><!-- FILES --><!-- SIGNATURE -->
Edited by huit on 09-30-08 09:06 AM.
By the way, a reinstall of Filemaker did NOT work. I had to install FM11 on a test machine and grab its certificate.