tp.index_set("fpinumber") = Incorrect data type

[forskare]

I have a dialog box where the user can select any one of five search catagories. It all works execpt for lines 97 - 100. The field "Fpinumber" is in another table, "t_findings". This is the part of the code where I'm getting an error message: Line 99: Arguement is incorrect data type. I checked the index name, spelling, table name, etc., all is correct. Where or what am I missing?

Thanks much,

kenn

94 case rslt = "okmx"
95 topparent.index_set("maxis_numbe")
96 topparent.find(Maxisnumber)
97 case rslt = "okfpi"
98 tp = table.open("t_findings")
99 tp.index_set("fpinumber")
100 tp.find(fpinumber)

[Al Buchholz]

Re: tp.index_set("fpinumber") = Incorrect data type

Kenn

What is tp.index_set()?

Do you mean tp.index_primary_put("<indexname>")?

Is the snow clearing out up there yet??? It's warm down here at the south end of Wisconsin...

[forskare]

Re: tp.index_set(&quot;fpinumber&quot;) = Incorrect data type

Kenn

What is tp.index_set()?

Do you mean tp.index_primary_put("<indexname>")?

Is the snow clearing out up there yet??? It's warm down here at the south end of Wisconsin...

Hi Al,

Using tp.index_primary_put("fpinumber>")

moves the Incorrect Data Type to the next line,

tp.find(fpinumber)

The ice finaly went out 12 days ago. Everything is about 3 weeks behind.

Thanks,

kenn

[Finian Lennon]

Re: tp.index_set(&quot;fpinumber&quot;) = Incorrect data type

As Al pointed out, you're mixing form and table methods.
topparent.find() will work on a form. Using a table pointer you need a table pointer method like tp.fetch_find() or tp.fetch_goto().

[Al Buchholz]

Re: tp.index_set(&quot;fpinumber&quot;) = Incorrect data type

Finian

Thanks. You explained Kenn's dilemma better than I.

[forskare]

Re: tp.index_set(&quot;fpinumber&quot;) = Incorrect data type

My form is based on a 2 table set, t_clients (parent) and t_findings, the child linked one to many. The user will select one of five fields in the dialog box to search for a record. Four of the five fields are in the parent table and the other is in the child table. The code for the four in the parent table works well but it's the fifth one that is stubborn.

Earlier, Finnian and Al said I cannot mix form and table methods. Are you saying that the code for the table method must be on a separate button?

Also, since the form is based on the set, the child table is open, right? Should I not be able to refer to the child table? If so, what is the correct syntax? I've tried various code but so far, no success.

Thanks for the help.

kenn

[Al Buchholz]

Re: tp.index_set(&quot;fpinumber&quot;) = Incorrect data type

Kenn

Go back to the help file and look at the table methods and the form (<object>) methods.

Then use a table pointer with a table method.

Or use form methods without using the table pointer.

That's where the mix up is.


ie
table pointer is tp
form method is index_set()

so as Finnian suggested, use
tp.index_primary__put("<indexname>")
tp.fetch_find(<valuetofind>)

or

topparent.index_set()
topparent.find()


but don't mix them together.... they are like oil and water.

[MikeC]

Re: tp.index_set(&quot;fpinumber&quot;) = Incorrect data type

Ken,

Also, since the form is based on the set, the child table is open, right? Should I not be able to refer to the child table?

Correct But Alpha does not necessarily know about the set when using the table methods---in this case you can first open the parent of the set, then the child...Alpha will then Know of a relationship (a "guru" one time told me to do this in a similar situation and sure seemed to work fine!). OR use maybe <TBL>.CHILD_GET() if that doesn't work.


LATER:

Earlier, Finnian and Al said I cannot mix form and table methods. Are you saying that the code for the table method must be on a separate button?

I think it means to use ONE then the OTHER....just not mixed together--same button but different part of the script.

[CALocklin]

Re: tp.index_set(&quot;fpinumber&quot;) = Incorrect data type

Hopefully I'm not beating a dead horse but I think a bit more clarification might be helpful.

Earlier, Finnian and Al said I cannot mix form and table methods. Are you saying that the code for the table method must be on a separate button?

No, feel free to put them all in one script. Just don't use one when you should be using the other.

.find() is used with forms.
.fetch_find() is used with tables.
They are similar but not interchangeable.

.index_set() is used with forms. (Also, .index_setverify() )
.index_primary_put() is used with tables.
They are similar but not interchangeable.

Also, since the form is based on the set, the child table is open, right? Should I not be able to refer to the child table? If so, what is the correct syntax?

Can you refer to the child table? Yes. But NOT with table.open(). I believe that many of us were doing that for years when we should have been using something else. Table.open() opens the table in a completely different session that doesn't know anything about what is happening in your form. You can use many other methods but you do have to be careful. If multiple forms are open, I believe the table.get() will refer to the parent form but I'm not sure.

tp = table.get("<ChildTableName>")
But, if you have multiple forms open and two or more happen to use the same table, which one will you get? My guess is that it would be the one in the current form but I'm not sure. If the table isn't in the current form, will it get it from a different form?? What if two different forms use that table?? (As I said, you have to be careful how you use these commands.)

tp = parentform:tables:<ChildTableName>.this
or, probably easier in many cases (I use this a LOT now - didn't used to):
MyVar = parentform:tables:<ChildTableName>.<FieldName>

A modification of the above when you have multiple forms open:
fp = form.view()
.....
MyVar = fp:tables:<ChildTableName>.<FieldName>

tp = table.current(<slot number>)
I don't like using this last one except when refering to only the topmost table (i.e., just tc = table.current() with no slot number ) because I've been known to modify a set and mess up all the slot numbers then have to go back and change all scripts that reference any changed slot numbers. What a nightmare!

tc = table.current() can be used in the FIELD rules and will ALWAYS refer to the table that the field rule is in. I use this for "standard" scripts, some of which are set up as keyboard macros such as this script I use in the CanSave event of many of my tables - it takes 3 keystrokes to type this, including the comment, using a keyboard macro:

tc = table.current()
tc.change_dtf = date()
'used only if a *script* creates the record but doesn't include the creation date:
IF tc.create_dtf = {}
    tc.create_dtf = date()
END IF

If you use table.current() in forms, buttons, etc. (outside of field rule events) then it's up to you to be sure it's refering to the correct table.