Bad Object Handle

[Zod Mansour]

I followed the suggestion of using action scripting to open a form and look into a field to match a record on the target form. If I open the form without any matches the form opens but when I chose a match that Action Genie offers I get a bad object handle! Anyone has had this?

thx,
Zod

[Selwyn Rabins]

RE: Bad Object Handle

zip up your app and let's take a look at it.

your code might be referencing an object after the object has been closed.

[Zod Mansour]

RE: Bad Object Handle

The interesting thing is that I am just using the Action Genie. So it should do the proper checkings. The files are attached.

thx,
Zod

[Tom Cone Jr]

RE: Bad Object Handle

I see the problem you are having. The "Statement" button on the Customer form generates it.

Using the latest build on my Win XP Pro system I created a new form for the "Statement_set" using the default form for the set as the template. No other changes to the new form occurred.

I then dropped a new button on your Customer form and used Action Scripting to open the new form. I used the option to limit the target form's range of records to those where the ID field in the Statement_header table matched the Cust_id field in your Customer form. It worked fine.

At this point I can't tell you what's wrong with your form or button. I suspect corruption in the called (target) form.

Recommend you verify you have the latest build of A5V6 and then try again with a new target form.

-- tom

[Selwyn Rabins]

RE: Bad Object Handle

the problem is not the xbasic generated by the genie on the button that opens the form.

the problem is the xbasic that you wrote in the onInit event of the 'statement' form.

you have

Var-"Month.value=left(cmonth(date()),3)
Var-"Year.value=cyear(date())
topparent:Month.value=Var-"Month.value
topparent:Year.value=Var-"Year.value
topparent.refresh_fields()


this xbasic is incorrect because:

1. you have a variabled called 'month'. however, the control that displays this variable on the form has a name of 'month0' (which you will see if you right click on the object and select Properties and then go to the 'setup' tab.

you can't reference the .value property of a variable name. variable names don't have any properties. so a5 is telling you that var-"month is not an object (the 'bad object handle' message is, i would have to say, a little cryptic, but it does make sense)

what you have to say is

month0.value = left(cmonth(date()),3)

since 'month0' IS an object.

as a matter of personal preference, I generally set the .text property of controls because that way you don't have to know what the variable's data type is. the text property is always character.

so i would rewrite it as

month0.text = left(cmont(date()),3)


similarly

Var-"Year.value=cyear(date())

becomes

year0.text = cyear(date())


because 'year0' is the object name

then, you can delete the next two lines (i don't understand what these were meant to do)

topparent:Month.value=Var-"Month.value
topparent:Year.value=Var-"Year.value

[Zod Mansour]

RE: Bad Object Handle


Thanks for the info. Very helpful indeed.
You mentioned the text property of a control. Can't find much info on this property in the help files. Is the text property the displayed label? Or is this text property the same as value but converted to character? Does it get displayed on the form when changed?

thx,
Zod