Field Rule Post Does Not Work

[Alan Lee]

Re: Field Rule Post Does Not Work

Bug? Seems significant to me.

[MikeC]

Re: Field Rule Post Does Not Work

Alan,
I have not looked at your sample yet but you mentioned

this makes believe the problem has something to do with the set field values command.

I have found many times where "Fields--Set Field Values" will not work consistently and so have used "Objects Properties--Set Properties of Object(s)" instead and it has not ever failed.


LATER: Did a bit of looking and notta . Too late to check more--shoulda waited til the morn anyway

[Alan Lee]

Re: Field Rule Post Does Not Work

Mike,

Thanks for the reply. Did you have a chance to test it? Do you see what I mean? I tested it using "Set Object Properties" and it does the same thing for me. It will change Qoh, Price, and calculate Value in the IMU form for the IMU table. It will correctly post Qoh and Price to the IMU_VALUE table. But it will not post the calculated value for the field Value to the field of the same name in the IMU_VALUE table. I posted a script on this thread earlier, that mimics the keystrokes that you would do if you:

1. Placed the from in change.
2. Activated Qoh and put a number.
3. Tabbed to Price and put a number.
4. Saved the record.

It works in every way. Everything changes and gets posted properly. But, I can't seem to figure out why the simple script does not work. I would think that this would be causing some one else a problem.

Thanks again!

[Tom Cone Jr]

Re: Field Rule Post Does Not Work

I would think that this would be causing some one else a problem.

Alan, it's never bothered me because I never uuse a script to assign field values to objects in form layouts in order to have them "posted" to a different table by field rules. If I'm going to the trouble to write a script that assigns field values to one table, I go ahead and write the desired results into the second table using the same script. To me writing the field values to the two tables is more direct and efficient. Assigning field values to objects in a form in order to have the table field rules post them to the second table seems unnecessarily convoluted.

[Alan Lee]

Re: Field Rule Post Does Not Work

First, in my particular application it makes since, at least in my mind. The application is for monitoring productivity of warehouse people pulling orders. An order entry person enters the order number and lines to be pulled. These orders are displayed via a embedded browse on a master form. The order puller double clicks on the order and a from opens showing the information about the order. They click a button to set the field value of start time for when they start pulling the order. When they are finished, they do the same thing except now they click a button for stop. Two fields have been updated at this point start and stop. A third field pick time, which is calculated by stop-start is calculated on the order and needs to be added via a post to a field in the pullers record showing the cumulative amount of time the puller has been pulling orders. Seems logical to me. Unfortunately, it does not work.

Secondly, I find no where in any documentation that says you can not do this.

Thirdly, what is the difference, from computer point of view, between me typing the values in and me setting the values with either the set object value or the set filed value commands?

I used xbasic to make changes previously, but I could not consistently reconcile the cumulative pick times in the pickers table to the pick times on the orders. So, I thought I would try a different approach. Unfortunately, that did not work either.

I still think this is a bug.

[Tom Cone Jr]

Re: Field Rule Post Does Not Work

Whoa! Did not mean to upset you. Just wanted to answer your question (from my perspective) about why this doesn't seem to be bothering lots of other folks. Sorry.

[Alan Lee]

Re: Field Rule Post Does Not Work

I'm not upset. I promise! I apologize profusely for coming across that way. Just wanted to explain my perspective on the situation. I am very, very interested in your thoughts on the subject.

[Tom Cone Jr]

Re: Field Rule Post Does Not Work

Ok.

I'll take another look.

1) The btn script does not set the PN value. Is the button only going to be used for a new record. i.e. where the user has begun a new record, assigned a PN, and then pushed the button? Or, is the button supposed to begin the new record, too?

2) What do you want the button to do if the user is not entering a new record, but wants to change the QoH and Price fields using the button?

I'm trying to get the big picture and need to understand the exact sequences you need to behave correctly. The post field rule does different work depending upon whether it's dealing with a new record or changes to an existing record.

[Tom Cone Jr]

Re: Field Rule Post Does Not Work

order puller double clicks on the order and a from opens showing the information about the order. They click a button to set the field value of start time for when they start pulling the order. When they are finished, they do the same thing except now they click a button for stop. Two fields have been updated at this point start and stop. A third field pick time, which is calculated by stop-start is calculated on the order and needs to be added via a post to a field in the pullers record showing the cumulative amount of time the puller has been pulling orders.

The post field rule fires each time the order record is saved. Unless you're leaving the order record locked (not recommended) it will fire when the order is entered, but not pulled. When the start (pulling) time is entered by the button the post field rule will fire again. And, again when the end (pulling) time is entered. At least 3x if I'm understanding this sequence correctly. Does your calc field return zero if it can't determine the elapsed time? I'm wondering whether the post field rule is the right choice in this scenario. Seems like a lot of unnecessary traffic over the network to me.

I'm curious what is "posted" when start time and end time are both empty?

Next, how does your pick time calc field behave when only the start time is available? I would think it would bark at you because it can't compute the elapsed time without both being available.

[Alan Lee]

Re: Field Rule Post Does Not Work

Tom,
Before looking at the pick application part, I'm trying figure out why the sample form/button does not work. The principle is the same and less complex on the sample. I don't think the complexity of the pick application is the problem, the logic is the same. In both scenarios I do not want the person pushing "the" button to add a record. I want to set a value. If the sample will work, the other will as well. I can't see the reason why the script attached to the sample button1 does not work. Does my logic not hold true? If you open the default browse for imu and make a change or you manually press the keys, it works as expected. But, if you use the script to automate it does not.

Thanks!!

If you would like me to explain in person, send me a private message with your contact number and I will give you a ring. No problem if you don't.

[Tom Cone Jr]

Re: Field Rule Post Does Not Work

Alan,

The "value" property of objects in the current form is not generally available until the record being edited is saved. The "text" property of objects in the current form always reflects the text entered from the keyboard. I'm not sure this explains what we're seeing with your approach, but I think maybe there's a timing problem that's preventing the calc field from being computed in time for it to be posted.

I decided to do a more faithful job of replicating the input sequence that occurs when the Price and QOH fields are entered by hand. My modified script seems to work just fine in limited testing here. Suggest you try to break it and let me know how it goes.

-- tom

[Alan Lee]

Re: Field Rule Post Does Not Work

it works, but i can not put the form in design mode to see what the script does.

[gmeredith17]

Re: Field Rule Post Does Not Work

Have you opened the database in the runtime by mistake. This happened to me recently and I couldn't fathom what was happening until someone on the board suggested I may have opened it in the runtime.

[MikeC]

Re: Field Rule Post Does Not Work

Tom, Alan.

Tom am sure you know this but want to say it for Alan and others who may be following the thread.

The Field rules don't fire unless the Qoh (quantiity on Hand) or Price field's OnChange event fires and then saved---which does not happen when setting values with xbasic as is being done....I gave up on many of the simple field rules for this and the fact that Alpha error messages that are inherited with some rules...I still use them but in a very limited way.

[Alan Lee]

Re: Field Rule Post Does Not Work

no xbasic. i read where where field rules are not honored by xbasic. only from a form or browse, which is the case. if you look at the sample database, the one form, button1, you will see what I am talking about.