xsharp.eu

I think (!) i have the latest, installed maybe hours ago (the one not named "old"...)

BTW, is it really not possible to maintain a "boring" 3 number naming scheme? Major.Minor.Build?
I hate duplicate names...

Hi KArl,

Yeah, it's easier to follow on one hand, but it's cleaner to release a file with a simple filename on the other hand.
Thanks for the feedback, will have to ask more people to test this..

Ahh, I think I know what happened. Horst, did you include different sets of dbfs in your two different zips? I can reproduce the problem with the first set, but not with the second one that I initially tried with.

.

Hi Karl,

i´m with you!

- beside the same download names - why on earth is the download no longer a zip but a exe ? so i must always confirm that the downloaded exe is save ...
- i hope the latest download is the latest build, because it still shows 2.11.0.0 ...

regards
Karl-Heinz

Hello Chris and Karl-Heinz

Its the same database. In the first dbf i send the record 4669 is deleted and the seek will not find the 002100000001636
In the second dbf i send i changed the deleted record, i made a recall for 4669 and i deleted the next record 4670 and then it works normal.
if i delete 4669 and 4670 then also the seek doesnt work.

So Chris pls try it with the first dbf.

i think Karl-Heinz is right , its because the deleted record is the FIRST in the dbf when you look inside with dbaLite

if SetDeleted true or false has no effekt (both not found) on my computer

Horst

Hi Horst,

Horst wrote: Its the same database. In the first dbf i send the record 4669 is deleted and the seek will not find the 002100000001636
In the second dbf i send i changed the deleted record, i made a recall for 4669 and i deleted the next record 4670 and then it works normal.
if i delete 4669 and 4670 then also the seek doesnt work.

So Chris pls try it with the first dbf.

Yes, but you didn't mention that you included a modified dbf in your second post, so I was trying to reproduce the problem and couldn't manage to do that because of this. I realized what was going on later and have logged the issue for Robert to look into it: https://github.com/X-Sharp/XSharpPublic/issues/986

.

Hello Chris

Sorry for that, next time i will spend more time to prepare a clean and with less code example.

Horst

Hi Horst,

That's OK, it was a good sample containing everything (and then a bit more ) that's needed to reproduce the problem, it was just confusing that it was reproducible with one set of dbfs, but not with the other. In any case, thanks for reporting this!

.