Base the value of a control in a form on another calculated control of same form

[Bigdaddrock]

I have tried using the SetValue Macro to assign the value of a calculated control to another BOUND Control on the same form but have not been successful. I followed the exact format shown in MS Access help instructions.
The amount appears properly in the unbound text box (derived from data in a subform within the same form), however I cannot get that amount to then appear in a Bound Control's text box using the SetValue macro.
I am only doing it this way, since I do not know how to attach a calculated amount from the subform to directly populate a Bound Control.
(The subform contains a series of items on an invoice. The Main Form is the actual invoice, and I would like to record the total price of each of the item's costs onto a record associated with the Invoice.
I do not do code, and would like to know how I can do this using macros or just keying into a section of the Properties associated with the text Box.
Thanks for the anticipated help.
BigDaddrock

[Bigdaddrock]

@NeoPa
As much as I appreciate your assistance, I am disappointed to report that when I added the code, exactly as written above I still fail to get any change in the control "ShipTot". Note, that TotShipWt is a control in the subform entitled SubFormA. Does that have to be introduced in some way?
The reason I need to store this figure in the Table, is that if the shipping costs associated with the various weights change at a later date, I DO NOT want the values stored previously to change.
Thanks again for your continuing assistance.

[NeoPa]

I'm assuming that :

1. [TotShipWt] is a control on a form that is used as a subform for another form.
2. [ShipTot] is a control on the other form.

The code is associated with [TotShipWt] and the code refers to [ShipTot] via Me.Parent, which is a pointer to the form that the current form is a subform of.

I would expect this to work. If you see nothing wrong with my assumptions yet the code fails to work you may attach a copy of your database to your next post and I'll look at it for you.

When attaching your work please follow the following steps first :

1. Remove anything not relevant to the problem. This is not necessary in all circumstances but some databases can be very bulky and some things do not effect the actual problem at all.
2. Likewise, not entirely necessary in all cases, but consider saving your database in a version not later than 2003 as many of our experts don't use Access 2007. Largely they don't want to, but some also don't have access to it. Personally I will wait until I'm forced to before using it.
3. If the process depends on any linked tables then make local copies in your database to replace the linked tables.
4. If you've done anything in steps 1 to 3 then make sure that the problem you're experiencing is still evident in the updated version.
5. Compile the database (From the Visual Basic Editor select Debug / Compile {Project Name}).
6. Compact the database (Tools / Database Utilities / Compact and Repair Database...).
7. Compress the database into a ZIP file.
8. When posting, scroll down the page and select Manage Attachments (Pressing on that leads you to a page where you can add or remove your attachments. It also lists the maximum file sizes for each of the allowed file types.) and add this new ZIP file.

It's also a good idea to include some instructions that enable us to find the issue you'd like help with. Maybe some instructions of what to select, click on, enter etc that ensures we'll see what you see and have the same problems.

[Bigdaddrock]

Will comply, but am concerned you are making the issue more complicated than it is. I am only using a single form which contains the control ShipTot and the SubformA is included in that form. SubformA contains the control TotShipWt. I merely want to set the Value of ShipTot based on the latest value of TotShipWt.
Is that clear?

[NeoPa]

I was rather hoping you'd confirm my stated assumption rather than trying to re-explain the situation.

From what I understand of your explanation, there is no difference between that and what I stated, but I'm the one who needs to check with you (who should know) that I understand what you're saying.

My confirming what you say matches what I'm thinking (which I'm happy to do) doesn't really get us very far as I don't have your problem.

[patjones]

I'm sorry to jump in at this point, but after looking at all the recent posts, I do think that either the two lines of code I provided previously, or the code that NeoPa provided, should function in this situation.

I wonder if the problem is much simpler than we have been making it. Is the parent form a bound form? I ask this because there is a set of properties in a form's property sheet that have a pretty big impact on what you're allowed to do in a bound form. Namely, they are Data Entry, Allow Additions, Allow Deletions, and Allow Edits.

The recordset type setting (Dynaset versus Snapshot) can also impact whether you are allowed to do what you are attempting.

I bring all this up only because we've had a couple questions recently on this forum where these settings played a role in solving the problem.

Pat

[Bigdaddrock]

@zepphead80
By all means, jump right in!!
Yes, the form is Bound, and Yes the settings for Data Entry, Allow Additions, Allow Deletions, and Allow Edits are all set to YES.

[Bigdaddrock]

@Bigdaddrock
I thought I did reply to your assumptions, which were not correct.
You stated:
I'm assuming that :

1. [TotShipWt] is a control on a form that is used as a subform for another form.
2. [ShipTot] is a control on the other form.

My answers are:
1. Wrong. [TotShipWt] is a control on the subform of the active form (not used as a subform on another form).
2. Wrong. [ShipTot] is a control on the active form.
Does that clarify things?
And more importantly, would that revise your solution? I hope so, since I am still seeking a solution.
Thanks for your patience and assistance.

[NeoPa]

I think the confusion here comes from my use of the term "another form". I was intending this to mean other than the form already referred to in the text, rather than a form other than the active form. As such, we do seem to be agreeing. The active form, is referentially blank (it is undefined without context) so it could mean the subform to me (It would indeed as this is where the code is executing), but the main form to you.

I'm afraid that leaves us no further along I'm sorry to say :(

That said, I notice you say that .DataEntry is set to YES. When that is YES then .AllowDeletions and .AllowEdits are ignored and behave as if set to NO. .DataEntry is a special case for allowing only new data to be entered via a form.

I hope this leads in the right direction.

[patjones]

If you're willing to, post the file and I will take a look at it. Just strip it of any confidential data and follow the other suggestions in NeoPa's posting guidelines.

Sometimes we get into these length back-and-forth threads when the problem could've instead been diagnosed much more easily if it was right in front of us.

Pat

[NeoPa]

Oh, and just in case I was a little unclear, you last post (#17) was perfect. It indicated clearly exactly where the confusion was. From there it was cleared (unfortunately didn't result in a ready solution but confusion gone).

I didn't want you to take my last post as criticism. It was just explanation.

PS. I'm also happy with Pat's suggestion. If it's easy for you to post a copy of the db then we can look at it for you. I expect the solution will be much easier with it in front of us :)