Hi All,

Without going into great details just now, I would like to know if
anyone has observed this behaviour. I have a form with a child table-
frame that displays patient visit dates in date order. Under some
circumstances, all the year values display as the current year.

For example:

Correct values might be
11/11/1997
12/10/2001
22/5/2007

Table frame displays
11/11/2007
12/10/2007
22/5/2007

The only way to fix the problem is to restart Paradox.

It seems to happen when I have been using a calendar to locate a
particular patient visit but I am not applying a filter. I do a
qlocate and a resync and ask that the secondary index of the primary
table is set. There is so much code to go through I am jusk asking if
anybody has seen this to narrow down the possibilities.

Regards Paul.

PS: This is not a consistent occurrence so I don't think the code
above itself is the problem. Paul.

When I see data display that can't be explained I always suspect a damaged
table.

Run table repair on all tables involved.

Anders

On May 25, 4:17 am, "Anders Jonsson" <gt3TakeThisA... (AT) bredband (DOT) net>
wrote:
Yep, have run CS, no corruption.... also seems to be an intermittent
problem or I have not tracked down exactly what is causing it. Thanks
Paul.

OK,
I've done a little sluething and it seems the culprit is some code I
have long used for hilighting each record in the table frame as one
moves through them. If I delete all the code, the problem goes away.

Curiously it only seems to happen when the secondary index is reset on
the primary table sequentially using two different searching forms -
one uses "surname", the other calendar date based. Not one or the
other, by itself, no matter how many times I use them. Shame, because
hilighting the record looks quite nice. Guess I have to look further
at this.
Thanks Paul.

Paul:
FYI: The standard record hilight code does not work correctly with
searches. Perhaps you could disable the hilight during the search?
OzPaul wrote:

Thanks Mark, I have been using the Paulker code happily for years.
Last night I found this simple code posted by Eugen Levin way back in
1995 or there abouts, which so far seems to highlight the current
record without the unwanted side effects... Hopefully this is all I
need.
Regards Paul

The following code is assigned to the Record's action event...

method action(var eventInfo ActionEvent)
switch
case eventInfo.actionClass() = MoveAction :
highlighted.color = container.color
case eventInfo.ID() = DataArriveRecord :
if highlighted.isAssigned() then
highlighted.color = container.color
endif
highlighted.attach()
self.color = Blue
endswitch
endmethod

where

Var
highlighted UIobject
endVar

is declared at Tframe's level. That's all. I clicked everywhere
including scrollbars like crazy, and so far the algorithm looks
robust.
=================+================================ =================
Eugene I Levin | L... (AT) lh (DOT) pti.spb.su - to be used from xUSSR
St.Petersburg, | L... (AT) lh (DOT) ioffe.rssi.ru - to be used from the
Russia | rest of the world.