A follow up to the above, as I've just experienced another crash. The problem appears when I'm trying to work quickly, if I pause and ensure the type ahead catches up, then there isn't a problem. For instance, in this case, I was entering a string of 'IsEmpty () and IsEmpty ()' repeated; FMPA pauses during the entry of 'and', looks for all the various possibilities such as 'Array', 'ABS', 'Random', etc. until it realises I actually want 'and' then allows me to proceed. What I was doing was typing ' and ' then immediately pasting an IsEmpty () string that could be slightly tweaked, but FMPA couldn't keep up and subsequently crashed.
For now I feel I'm having to treat it like a fragile item and not try to work too quickly (great for productivity!).
Again, appreciate knowing whether this is just us, or whether others have similar problems. Crash report again below.
Faulting application name: FileMaker Pro Advanced.exe, version: 126.96.36.199, time stamp: 0x59372d1e
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18666, time stamp: 0x58f33794
Exception code: 0xe0434352
Fault offset: 0x00000000000095fc
Faulting process id: 0x27b4
Faulting application start time: 0x01d30d000f07a8db
Faulting application path: C:\Program Files\FileMaker\FileMaker Pro 16 Advanced\FileMaker Pro Advanced.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: a42deada-78fb-11e7-8148-005056b9858b
Faulting package full name:
Faulting package-relative application ID:
1 of 1 people found this helpful
I use FMPA 16 on Windows and while there are often delays waiting for auto-complete with complex graphs/lots of TOs, haven't been experiencing any crashes. (FMP 16 on Windows is actually the most stable Windows version in years.) Plug-ins and their external functions could cause a problem like that, but as you said it's more likely the pasting in additional text before auto-complete is done.
I do wish the calculation engine had exceptions to delay auto-complete for certain words like "and" and "or" until the trailing space is typed/not typed -- in any solution where there are "ord" (short for Order) TOs, there is a lot of waiting around for FM to figure out that's not what I'm looking for at the moment.
Thanks Marc, yes I agree.
There are some annoying/delaying nuances with the auto-complete that often don't make sense. We have an added problem with the plug-ins, we use the shortcuts extensively such as 'gtr' for 'Go to Record', etc. but as we depend on 360Works Scribe, using 'sv' for 'Set Variable' we get 'ScribeVersion', so are having to adjust our shortcuts say from 'sv' to 'var'. We did discuss this with 360Works' (excellent) support and apparently there is nothing they can do about it.
Certainly focus now needs to be on speed now that it is working.
Thanks for the contribution.
I have not experienced crash but like Marc I have experienced delays.
Corrupt objects on a layout or corrupt item in a container field can cause FM to crash. It may be worth testing with a brand new database (starter solution) and verify that it crashes. If it does not crash you may have to rebuild a layout.