if you export the structure to XML and create a new DB from the XML,
you can open your production DB in "user mode", that is, with no custom forms
or code.
will 4D still crashes in that state?
what I am trying to say is that when 4D certifies a version for an OS, it means
every feature is properly tested, both automatically and manually,
it also means that the version has been tested and used for weeks in production
without a regression.
but I am sure you can understand how that won't necessarily certify every 4D
application code in production.
unless you know exactly which part of the application is failing,
and you have found a highly related problem in the fix list,
I don't think the issue is going to go away just like that.
having said that,
using a nightly build is always the preferred option.
(remember, it is not a "dev" branch like some people tend to imagine,
only verified changes are allowed to make it into the v15.x branch)
> 2016/09/08 11:04、Ronnie Teo <[email protected]> のメール：
> The version deployed is v15.2 while the OS is 10.11.5.
> Wonder why these stability issues are occurring when v15 is supposed to be
> certified on El Capitan.
> Would an upgrade of either or both help alleviate the uncertainty?
宮古 啓介
セールス・エンジニア
株式会社フォーディー・ジャパン
〒150-0043
東京都渋谷区道玄坂1-10-2 渋谷THビル6F
Tel: 03-6427-8441
Fax: 03-6427-8449
[email protected]
www.4D.com/JP
**********************************************************************
4D Internet Users Group (4D iNUG)
FAQ: http://lists.4d.com/faqnug.html
Archive: http://lists.4d.com/archives.html
Options: http://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
