Tab Order Bombs

[RodM]

I am now running v12 v.03,    love it but.... it crashes... doing the same.. in version FM 11 for years never never a crash

 

  have  Win 7     good equipment.. everything pretty up to date etc         Took the files to my Laptop with FM 12.... didn't happen as often... thought everything was fine... then it crashed too same place  selecting Tab Order

 

 

Today .. after modifying a layout,  I regularly now when I click the    Tab Order button,,     

M 12 crashes...    no error message.   

 

 

Secondly,  another error message, usually after..if trying to just start FM up again,  without any kind of recovery as above

.. Error R6025   Pure virtual Function Call ?

 

 

 with my app includes both program  AppProg.fmp.12       has a few files

  and my data        AppData.fmp.12       where most my data or 20+files

 

After a crash    I restart FM12    run AppData

Then File/  Copy AS      to a /CleanFolder    AppData1

Then File/ Recover     choosing AppData1

 

Then do same for other file

 

Then File/  Copy AS      to a /CleanFolder    AppData1

Then File/ Recover     choosing AppData1

 

 

This not fixing .. as some suggest... or reading blogs,  

 

no images.  by reference, and disabled too    and  webview off   etc.. 

 

 

continues to happen?

 

 

Now I am looking what more can i do?

 

 

Thanks... 

 

 

 

 

 

 

 

 

 

[Adam M.]

I had this exact same problem.  In my case it was a file converted from an earlier version that I tried to convert to the new .fmp12 format.  The closest I ever got to nailing it down was stripping everything out of a duplicate of the problem file.  It seemed (again, in my case) specifically related to a button that I had that was filled with an image and changed to no fill based on conditional formatting.  Everything worked just fine, but as soon as you tried to set the tab order, crash.  Fortunately, I was at the beginning of rewriting this project, so I just created a new file, then copied the tables, scripts, etc. over.  Never happened again.  I did submit the problem to FM.  Never heard anything back.