"Gene Wirchenko" <genew@[EMAIL PROTECTED]
> schrieb im Newsbeitrag
news:7d03o35qfe3vt9sjlb4obdtm82qrscgn80@[EMAIL PROTECTED]
>
>>Then I'd have a look at all involved tables and their CDX files.
>
> They seem to be fine though I really do not know what to do to
> check them. I opened the table and listed it with each of the tags in
> effect. I saw nothing odd.
I'd probably try to (backup the real table files and) create a new
test.DBF (and CDX) from scratch, adding only a few lines of test
content first and later the entire content step by step.
Beyond that, I'd try a DBF Repair tool like Abri "Recover" or "FoxFix".
> Sometimes, the code works, and sometimes, it does not. One point
> that I have not mentioned previously. When the code fails, it fails
> at the beginning of the browse. First, the browse grid appears, then
> the contents do. I usually get some of the contents, then boom! I do
> not recall a case where the browse has blown up after it has completed
> its initial display.
So you've got a quite complex Browse statement but do not use the
"Last" clause (because Set Resource is Off), right?
Can you track down the error to some data dependencies, e.g.
suspicious content like say filter results containing .Null. values or not
or Length() of certain content exceeding some limits like the 120/240
difference depending on Set Collate?
> I have not been able to figure out a pattern. In following your
> suggestions, I finally did get an error indicating a statement in the
> browse function method. (Previously, they have been for the browse
> statement.) It turned out to be the SQL-select. That did not help.
Do you use Cast() for all calculated columns to avoid truncation of
fields in subsequent rows depending on the first line found by the SQL
engine?
> I think that I have some sort of Heisenbug here. For example, I
> tried set coverage, and it changed the behaviour of the program!
Hu! <s>
hth
-Stefan
--
|\_/| ------ ProLib - programmers liberty -----------------
(.. ) Our MVPs and MCPs make the Fox run....
- / See us at www.prolib.de or www.AFPages.de
-----------------------------------------------------------
|
