What's The Cause?

[forskare]

I have a button on a single table form. It brings up a dialog form. As soon as I select a name and click the form's Close button, the whole db locks up and I have to Ctrl-Alt-Delete. This works great on the parent table of a set but the single table isn't feeling too well?

f=form.view("QrySearch Form","dialog")
job=f:Tables:acctitems.case_name
f.close()
parent.index_set("case_name")
parent.find(job)

Does anyone have a suggestion as to why the lockup? I've dbl chceked the index name, field name, etc.

Thanks,

kenn

[Jim Chapman]

RE: What's The Cause?

Hi Ken,

Put a debug(1) command in here and see what's going on. You are dealing here with indexes, have you rebuilt the index to check for corruption in the index? Why are you looking to the table rather than reading off the dialog form? I'm wondering here if you've commited the form, saving the value to the table or not, assuming that a user is typing in a value here. It appears you are just bringing up the form without any criteria for the record it will contain, so probably you are fetching the first record in . Is this what you want? It should be apparent using the debug(1) command what is going on.

Good luck,
Jim

[Stan Mathews]

RE: What's The Cause?

Ken,


All the examples in the documentation use

parentform.index_set("tagname")

While the parent of the button is the form, it might help to try the more explicit parentform.

Also the .find() method is demonstrated in use with form pointers, like

frm = :form.load("customer_dlg", "dialog")
cust_id = parent:browse1:cust_id.value
frm.index_set("cust_id")
frm.find(cust_id)

or parentform.find()

it is not shown as parent.find().

Also I certainly hope you don't have a form named
"QrySearch Form".

Why compound possible problems by using "reserved" words like "form" and leaving spaces in the form name?

Probably all wet here, but may help.

Stan

[forskare]

RE: What's The Cause?

Jim,

The dialog form contains an embedded browse from the table which has a name field. Again it works fine on a form based on a set.

I'm working with the debug but when I type the i or j and hit F-12, nothing happens. The indexes have been rebuilt.

Thanks,

kenn

[forskare]

RE: What's The Cause?

The form and browse are based on a single table. The table contains all the records for every name in the parent table. My goal is for the dialog form to pop up all the names, make a selection and by making that selection, all records 'NOT' associated with the name are filtered out.

Jim asked, "Why are you looking to the table rather than reading off the dialog form?"

The dialog form is based on the parent table because the dialog form has an embedded browse which show the names and case numbers. When used with a form based on the set, this works fine. The search dialog form has to be based on the parent table or there'll be a name for each record. That, I believe, is where I'm running into my problem.

I've been working with Stan's suggestion but, haven't been able to get it to work. Perhaps I'm going about this the wrong way.

Thanks,

kenn