On Mon, 13 Jul 2020 20:25:53 +0200, Aladino wrote:

Today I tried to update with FMPA 18 an old solution I made originally
with FMPA 9, but updated more times until FMPA 15. To make the solution readable from developer utility, I modified the data file extension to "fmp12", and the file works fine with FileMaker Pro 18. And seems to
create the runtime solution normaly. But after I've created the solution
and try to lunch it, it crashes immediatly. And I get the same behavior
on both my Macs... one with Mojave and one with HighSierra.
Is there someone here that has an idea whath can cause this issue? If it
can be usefull, I can past crash report here.
Reopenin solution data file with FMPA 18 seems to work flawless (with or withouth modifing the file extension).

don't just change a file extension. It's best to open the old file with
a new version as an old file and to convert it this way to a new
version.

If files would just be readable between versions, there would not be the
need to invent a new file extension. It's suprirising to me that it
opened at all - but it's a good chance to corrupt a file this way.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Today I tried to update with FMPA 18 an old solution I made originally
with FMPA 9, but updated more times until FMPA 15. To make the solution readable from developer utility, I modified the data file extension to
"fmp12", and the file works fine with FileMaker Pro 18. And seems to
create the runtime solution normaly. But after I've created the solution
and try to lunch it, it crashes immediatly. And I get the same behavior
on both my Macs... one with Mojave and one with HighSierra.
Is there someone here that has an idea whath can cause this issue? If it
can be usefull, I can past crash report here.
Reopenin solution data file with FMPA 18 seems to work flawless (with or withouth modifing the file extension).

--
Per rispondere, togliere -NOSPAM- dall'indirizzo.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Martin ?rautmann <t-usenet@gmx.net> wrote:

I tried just now to create a runtime solution with a new file created
starting with a template. And I get the same behavior.
Problem seems not to be related to my specific solution.


--
Per rispondere, togliere -NOSPAM- dall'indirizzo.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Martin ?rautmann <t-usenet@gmx.net> wrote:

don't just change a file extension. It's best to open the old file with
a new version as an old file and to convert it this way to a new
version.

Mybe you didn't understand me. I changed the file extension I used for
runtime solution, but file format is always fmp12.
In any case, I found the original Filemaker pro 15 data file, and using
it to build a runtime solution gives the same result.

--
Per rispondere, togliere -NOSPAM- dall'indirizzo.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Martin ?rautmann <t-usenet@gmx.net> wrote:

don't just change a file extension....

Thanks for your help, but I found that the issue and the solution (or
better, a workaround) is described here:

<https://fmforums.com/topic/105327-runtime-troubles/>

--
Per rispondere, togliere -NOSPAM- dall'indirizzo.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Aladino <borgobello-NO@SPAM-alice.it> wrote:

Thanks for your help, but I found that the issue and the solution (or
better, a workaround) is described here:

But this could be a better workaround (but in any case a workaround,
really disapponted with Claris that won't put a patch on this):

<https://support.claris.com/s/article/Runtime-solution-crashes-upon-launch-on-macOS?language=en_US>

--
Per rispondere, togliere -NOSPAM- dall'indirizzo.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)