Strange behaviour using Scan
Ian Espie
In an application that was working well in the past - not sure what has
caused it to stop working well now. I am using Pdox10sp3 on Windows XP. I
am using Scan... endScan to find records in a table containing 4000 records
and then change a specific field value. The scan works well for records
near the top of the table, as one goes lower down the table the scan's
behaviour changes - it finds only some of the records and not all of them.
Near the middle of the table it just hangs and I have to re-start Pdox. I
have checked the integrity of the table - its OK.
Does anyone have any suggestions as to why this could be happening? - is the
table too big to run the scan? Is there a more stable way of doing it than
using Scan? Thanks.
Bertil Isberg
Ian
<<
I have checked the integrity of the table - its OK.
>>
Did you rebuild the table. Verify does not report all problems?
<<
Does anyone have any suggestions as to why this could be happening? - is the
table too big to run the scan?
>>
Table is not too big. Do you happen to change the key field?
--
Bertil Isberg - CTECH
Paradox buglist:
online: http://w1.826.comhem.se/~u82608896/
FAQ newsgroup: corel.wpoffice.paradox-faq
Ian Espie
Thanks for the reply Bertil,
Yes I did rebuild the table and also the table to which it is linked by
referential integrity.
No the keyfield has not been changed.
"Bertil Isberg" <bertil.isberg@NOcomhemSPAMdotse> wrote in message
news:41a9b56e_3@cnews...
Ian Espie
I think I have found the problem. I add some "table lookups" to the table a
few weeks ago. I have removed all these lookups and now the scan works
perfectly. I am not sure what is wrong with the lookups to induce the scan
to behave strangely.
"Bertil Isberg" <bertil.isberg@NOcomhemSPAMdotse> wrote in message
news:41a9b56e_3@cnews...
>
Ian Espie
Thanks for the reply Bertil,
Yes I did rebuild the table as well the table it is linked to by referential
integrity.
No I have not changed the key field.
"Bertil Isberg" <bertil.isberg@NOcomhemSPAMdotse> wrote in message
news:41a9b56e_3@cnews...
>
GeneM
Ian Espie wrote:
> I think I have found the problem. I add some "table lookups" to the table a
> few weeks ago. I have removed all these lookups and now the scan works
> perfectly. I am not sure what is wrong with the lookups to induce the scan
> to behave strangely.
So perhaps some of the field edits violated some lookup rules. If you
track the Unlock record action, as Bertil suggests, you may be able to
track down the lookup conflict (or key violation?).
-- GeneM
Bertil Isberg
Ian
After changing a field, do you unlock the record?
Steven Green
Ian Espie wrote:
> and when these records got edited during the scan process - there was
> conflict and the system just hung.
the system didn't hang.. the cursor was sitting in the offending field, waiting
for you to correct the invalid data.. error trapping when posting would have
exposed the error..
--
Steven Green - Waldorf Maryland USA
Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales - Corel CTech Paradox
---------------------------------------------------
Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Trading Cards and other Sports Memorabilia
---------------------------------------------------
Ian Espie
Yes thanks - you are absolutely correct. Some of the fields where the
lookups were applied had old data in them which did not match what was in
the lookup tables - and when these records got edited during the scan
process - there was conflict and the system just hung.
Once again - thanks for your suggestions.
"GeneM" <NoS...@NoYahooSpam.bom> wrote in message news:41aa2788_3@cnews...