Hi there,

in a form I want to use as a lookup-form I have a problem with the seek-method, which does not seem to work.

On the form, the BO "LieferöookupBO' is filled in the parentformloading-event.

The calling form, which activates the lookup-form, send a search-parameter, which is

assigned to a private form-var. In the Load-Event I tried my seek-implementation:

If cSuche.Length > 0 Then

Dim lRet As Boolean

MsgBox("Count: " & LieferBO1.Count.ToString)  ' Just testing, if the BO is filled. It is.

lRet = LieferLookupBo.Seek("adresse='CLA'")   ' Hardcoded just fpr testing purposes.

If lRet Then

MsgBox("Found: " & LieferBO1.ADRESSE) ' Has not moved the current row index, not showing "CLA"

Else

MsgBox("Nothing")

End If

The search happens on a table containing lookup-codes like:

ASAP

AVA

BM

CLA

Now what happens is, that seek returns True, as if if has found "CLA" but the current row index has not changed (as described in the help-file) as the "ADRESSE"-property of the BO is showing the first code in the table "ASAP".

Can anybody tell me. what is going wrong there.

Best regards

Thomas

Hi Edhy,

thanks for your explanations. I dio something similar with some forms like my customer- or my article-editing-forms which can be called from different places and this is working fine. All these forms have in common that the tables used on the childform are alo used on the parent form and the childformdialog does the translation to the childform.

But in this special case which started the thread I don't use the lookup-data (supplier-codes) on the parent-forms which call the lookup-form, so I don't understand why I should there use a childformdialog when it is (now, following Trents advice) working?

Best regards

Thomas

Hi Thomas,


You don't have to use a ChildFormDialog in all situations.  I was simply explaining how I use it and I prefer to stick with the framework tools as much as I can for several reasons, one of them to keep the source code as standard as possible.  I have cases where I used the ChildFormDialog with no BO to do some process and simply return OK or Cancel, so that is the beauty of the ChildFormDialog that it will not lock you to use it for one purpose only.

Edhy Rijo

Hi Edhy,

<< have cases where I used the ChildFormDialog with no BO to do some process and simply return OK or Cancel, so that is the beauty of the ChildFormDialog that it will not lock you to use it for one purpose only. >>

Thanks for that nice idea.

Best regards

Thomas