I originally posted my problem on foxite: http://www.foxite.com/archives/0000340507.htm.
I've narrowed the issue to only happen when I am running FoxTabs. I have been running FoxTabs for over 2 years now and I love it (remember that we met at SWFox). But, I am pretty frustrated now that I've run into the issue.
I can consistently hit the error if I type the line:
crit='faiid=famid AND faioid=famoid AND !DELETED()'
As soon as I type the open parenthesis, '(', I get the fatal error, exception C0000005. I have reinstalled VFP and FoxTabs to no avail. I'm thinking that something with FoxTabs is killing intellisense, but you may have a better insight.
Joel's response:
Thanks for the report. I have been able to reproduce this one. Every now and then, and odd case like this pops up with FoxTabs. In your example, you have to have two comparisons inside a string followed by !DELETED() entered in the same case as your Intellisense settings, then it will crash. One comparison – no crash. DELETED() in a different case – no crash. Put spaces around the first equal sign – no crash. So, it’s an odd combination that no one would guess could cause a problem, and there are plenty of workarounds. But that’s no consolation when you’ve just lost some of your code. I’ll look into this for the next release, and see if I can track it down.
Thanks,
Joel
I have since quit using FoxTabs as I never put spaces before and after an equal's sign. Also even though there are other workarounds, I'm a person that will not use a tool that loses code. Once this is fixed, I will love to use it again!
Comments: ** Comment from web user: Steingo **
I have discovered another scenario that triggers a fatal error. I wanted to edit this line:
lcVarName = ALLTRIM(tQuery.Identifier)
to this:
lcVarName = UPPER(ALLTRIM(tQuery.Identifier))
Positioned the cursor in front of ALLTRIM and typed UPPER( - as soon as I hit the parentheses, it crashed VFP. I paused FoxTabs and tried it again, no problem. Also, with FT on, I can type the whole line in without crashing - it's only if I insert UPPER into the existing line. I can also avoid the crash by typing upper in lower case (is that an oxymoron).
Don't know if this will help identify the pattern that's triggering this, or just complicates matters, but it would be nice if this could get resolved. I do like FoxTabs but these cases are a little disconcerting - though still rare enough that they won't stop me from using it.
