Yes, you just can't leverage any new features of FileMaker 13.
FileMaker 13 can open databases hosted and created in FileMaker 12. You can continue developing and hosting in v12 with v13 clients accessing the file until you upgrade to 13.
Furthermore, you can do development in v13, and users from v12 can still access it. But if you try and place a new feature in from v13, v12 users will not be able to use or view that object/script step/function/etc..
Thanks for the quick reply. Big help.
Our SE in Asia-Pacific, in his recent series of webinars on FM V13, issued a strong caution over developing with V13 if you still have V12 clients accessing that solution.
I made the mistake of opening our in-house solution with FMPA 13, then opening one script to make a minor change only to have it fail on a critical step when next used by a V12 client. Copying the entire script from a recent backup was my way of restoring the intended behaviour.
My opening script for that solution now checks for a V13 client, issues a warning and closes the file.
Seems that there's still devil in the details.
Never said that I recommend it, just that it's possible. In a perfect world all people developing/hosting/accessing the file would be on the same version.
You should always develop in the lowest version accessing the file. so in a mixed 12/13 environment, use FMPA12 and FMS12 for hosting/development.
I share your sentiment though, tread cautiously when mixing it up.
Actually, I am doing the opposite, developing in and using it in 13.