Variable in table lookup filter

[milesjg]

Is it possible to use a variable in the filter for table lookup in field rules. ?
Every time I try in one form or another I get a A5 error (script error trap- "ui_dlg_box:select_field:name.db" where name is the name of the db in use.

[MikeC]

Re: Variable in table lookup filter

James,
Yes. I just did it.

:) Now that was a ton of help wasn't it!


I have a list of prices.
I declared a global variable for my form and added it as a field so to be able to create a value for it easily--you can set it via xbasic, etc many ways.

Using field rules lookup I used Table Lookup
On the filter I used: Price >= eval(Var->gvLookup)

I suspect you either did not use Var-> as a preface or needed the eval().

[milesjg]

Re: Variable in table lookup filter

Mike;

Thanks. That was a ton of help. Lets me know something else is going on.
I did/do it the exact same way and still have the problem. I should have said when I try it I get an error message of one form or another. It is not the same message every time. They are A5 system error messages. Some are the kind with line numbers. (2 different ones show, depending on how creative I feel with the filter.) I suspect something with the form or the db.

[Tom Cone Jr]

Re: Variable in table lookup filter

James, here's a debugging tip. Use the "default form" for your set or table to test the field rule changes. If it works fine there, but you hit errors in your custom data entry form, then you know that the problem lies in the form, not in the rules.

[milesjg]

Re: Variable in table lookup filter

Tom

You are correct. I need alot more "expereince" with debugging tips if Alpha and I are to coagulate properly. I should have tried it on another form before I whined about it. I applied it to another form and no go. I created a new form and no go. I deleted the table and created a new form and all was fine. I have to get into the midset of "crashes can = db/table/form problems" (sometimes) instead of A5 error, and work from that premise (sometimes). (I suppose one could call it an A5 "deficiency" when a line # error and code shows up instead of someting like a "table corrupt" message) but I don't. Not anymore. I've changed. Some say for the better.
Thanks for the tip. I will keep it in mind.