I reckon that
definately qualifies (-: (that's an antipodean emoticon)
Are you going to submit it or do you want me to?
Nice catch ...
Cheers,
Andrew
>I'm sorry, I read your message too fast. You are definitely correct. I did some testing, and could not reproduce your problem until- get this: I turned Strictdate back on. In dev mode, I always operate with STRICTDATE set to 0, to make things easy on me. When I set it back to the default setting of 1, I got the error you described. Setting STRICTDATE to 0 during the index process and restoring it to 1 afterwards avoids the error, and produces the desired results.
>
>I think this definitely qualifies as a VFP bug. How about you?
If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?
From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."
All my FoxTalk and other articles are available on my
web site.
Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.
