LiveBlock in SmartFetch

[Valgardur]

In the documentation it says that LiveBlock is default FALSE, however it defaults to TRUE when I drop a TOraQuery on my datamodule.

SmartFetch is not enabled (Enabled is FALSE), does that mean that the LiveBlock value is ignored?

Is it possible that the LiveBlock value could affect the .Locate on the dataset? I have a very strange behaviour where a record cannot be located in a dataset with SmartFetch off but LiveBlock on.

[AlexP]

hello,

Thank you for the notice. We will correct this information.
Yes, if smartfetch is not enabled, LiveBlock is ignored.
Please send a small sample demonstrating the issue with Locate to support*devart*com , including scripts for creating and populating the table.

[Valgardur]

Thanks for a quick reply..

I will investigate further.. this is an isolated incident in a complicated structure.. I just wanted to rule this out first.

Are there any known issues for Locate that might result in a record not being found?

[AlexP]

Such behavior may occur in case when Locate is used for search by text fields and the letter case doesn't match.

[Valgardur]

thanks, I was aware of case, but only numeric values...

[AlexP]

Unfortunately, we can't tell more definite reasons for such behavior without a sample reproducing the issue.
Try to use the LocateEx method https://www.devart.com/odac/docs/?devar ... tions).htm

[Valgardur]

I understand, thanks for a quick and helpful reply, I just wanted to eliminate any known errors or unexpected behaviour.

I'll probably eliminate the "locate" completely, using parameterized queries.. somehow never comfortable with "locate"

[AlexP]

If data is not filtered after setting the parameter, then locate will handle. If data doesn't match the parameter condition, then locate won't find it.

[Valgardur]

hi, all records from a table are retrieved - no filter, no parameters..

[AlexP]

Unfortunately, we can't tell the exact reasons for such behavior without reproducing the problem.