Thank you for your post.
I watched the video, but I am unable to replicate the problem on my Windows 7 machine.
Is this happening to just one file or all of your files? Since this is happening on three different machines, I would like to get a clone of your file as this will give me a better chance of duplicating the problem. I understand this happens at random, so if you can tell me what other actions you took prior to the crash, it might be helpful with my testing. I have sent you a private message (top of this page - right side - X Messages) with instructions where to send the file.
A sample file has been sent as requested.
Incase you cannot re-produce, ive included a vide of the sample file which again shows the issue..
This is using a brand new file created from a FM template about 1 hour previous.
I forgot to ask in the email, are you testing under windows 7 64 bit ?
Ive done some searching and come up with 'BEX' is to do with a Buffer Overflow Exception and is related to Data Execution Prevention in windows.
Source 2 :
However changing the DEP settings has no effect, either on for all with filemaker added as an exception ( so basically off) or on for essential programs and services.
If by the weekend there are no confirmations from either yourself or other forum users, I will perform a fresh install of windows 7 on my system and see if I can replicate the issue again.
Running Filemaker Pro 10 (not advanced) on the same machine but in using Windows XP mode in Win7
I am so far unable to reproduce the same crash.
Im doing some more testing on this at the moment... its beginning to really hinder my progress...
Right-clicking on my Windows 7 system, it does show
System type: 64-bit Operating System
I received your file, and I opened one of the scripts and scrolled to the bottom, and I immediately received the error message and crash. First time.
I have forwarded your file, this thread, and my findings to Development and Software Quality Assurance (Testing) departments for review and confirmation. I will contact you when I receive confirmation.
Thanks... at least I now know its not directly linked to my machine...
I can save myself a weekend of formatting and re-installing everything.
Just as a side note, I ran a recovery on a copy of the file a minute ago and no errors where detected either.
Out of curiousity, did you test the recovered copy to see if scrolling the script still crashes the file?
I've seen a few cases were recovering a file changed its behavior even though the process reported "no problems".
Just so you know, this works correctly with Windows 7 32-bit mode, as well as Windows XP, Mac OS X 10.5.8 and Mac OS X 10.6.2. It only appears to crash with Windows 7 64-bit.
Reply to PhilModJunk
Yes the same behaviour exists im afraid. Also bear in mind, I created a new file from a filemaker template.
Its not limited to one script, altough easier to reproduce in a long script with lengthy content such as calculations.
At first I thought the perhaps it was the scripts at fault or some form of corruption, so I re-created them from scratch, but the same issue persisted. Altough the video I posted doesnt show it, the one I sent to TSGal also showed the same file, with the same script not crashing when scrolling through a number of times.
Ive sat there for about 15 minutes re-opening the file, editting the two long scripts and scrolling to my hearts content without a crash... Then just as I think something ive been trying has solved the problem... crash !
It can go hours without a crash, then all of a sudden a new script im working on will cause the crash as soon as I scroll..
Its extremely unpredictable....
No other scrollable window causes the crash apart from those viewing the contents of scripts.
Ive even gone as far as removing 6gb of ram to see if it was a memory issue (leaving 2gb)
At least now TSGal has experienced it too.
Reply to TSGAL
Thanks for the additional info, that may explain why its ok under Windows XP mode (virtual pc) on the same machine.
I have received confirmation from Testing that this is reproducible on Windows 7 also in 32-bit mode. There is still further testing occurring as they are trying to get more examples. If you have a couple of other clones exhibiting this problem, please send them to the address provided in the previous private message. Thanks.
I will see what I can do, it shouldnt be too difficult, since I created this file fresh and immediatly reproduced the error.
A new file has been sent as requested.
Again, this one is a brand new file with 1 field and no records.
The script was created by manually adding 5 script steps then duplicating these steps.
I can create as many new files as you need, but there doesn't seem to be any point.
You can create crash-able files yourselves by simply making some long scripts, with long script steps.
All I know for sure is... its not my solution files corrupt, so at least this is a relief.
On that note... when making a test file, and having it crash on me, the file became damaged and was unrecoverable.
It gave me a message about account privelages etc (cant remember entire message sorry)
For this reason alone (and considering it has now been confirmed on more than my machine)
Filemaker should update their knowledgebase and recommend against using Windows 7 with Filemaker for development
until the problems are resolved by which time, we will probably have to pay for a major version anyway !
Thank you for sending another file along with the log file. This has also been sent to Development and Testing.
I have alerted the persons responsible for the Knowledge Base Articles, and I requested that Article #7454 be updated.
I just ordered a new computer with 64-bit Windows 7 (32 was not an option). I am currently using FMP 7, which is probably not compatble with W7. I am wondering whether I will have any problems with FM10 on W7 64.
This problem documents one such problem. This issue is extremely likely to be applicable for both Filemaker 10 as well as advanced.
Another item to read: