Instructing two way data exchange?

[andycaps]

Hello

I have set called Inventory comprising of tables

Inventory:

VendorPrices

Products

In the table: VendorPrices I have the following fields:

• Vendor
• Product_ID
• Price_1 (numeric)
• P1_Set (logical)
• Price_2
• P2_Set
• Price_3
• P3_Set
• Price_4
• P4_Set

The Price_1 to Price_4 fields are all populated with a various value for the same product.

The P1_Set to P4_Set fields are logical fields used to select a price, only one logical field can be set for each Product_ID



I need help/advise with:

1. Only one logical field can be checked at one time, thus how can I enable the process to: when checking the logical field linked to a price field it automatically un-checks a previously checked field, meaning all the logical fields can remain unchecked or only one at a time can be checked, I want to disallow the possibility of a user checking 2 logical fields for the same product.
   
2. When a logical field is checked it sends the cost value of the assigned Price_? field to the ‘Price’ field in my Products Table?
   
3. When a logical field is un-checked it removes the cost value previously assigned

to the Products Table: Price field?


Any help would be great
Thanks
Andy

[Stan Mathews]

Re: Instructing two way data exchange?

1. Only one logical field can be checked at one time, thus how can I enable the process to: when checking the logical field linked to a price field it automatically un-checks a previously checked field, meaning all the logical fields can remain unchecked or only one at a time can be checked, I want to disallow the possibility of a user checking 2 logical fields for the same product.
   
2. When a logical field is checked it sends the cost value of the assigned Price_? field to the �Price� field in my Products Table?
   
3. When a logical field is un-checked it removes the cost value previously assigned

to the Products Table: Price field?

1) Presumably the user would be viewing a form where the logical fields are represented by check boxes? These form fields have values (.t./.f.) and they have events. You are interested in setting the values and the triggering event would be the onchange for any/each one of them. IOW changing the value in one to true should set the others to false. Changing one to false should not affect the others.

2) 3) The onchange event could also be used to do this.

[andycaps]

Re: Instructing two way data exchange?

Hi Stan,

thanks for this. I was thinking of displaying the product ID and Price information in a browse, see enclosed screen shot.

As you can see from the example - the first item is checked twice, it is this i want to stop happening as well as sending the price details to the products table.

Andy

[Stan Mathews]

Re: Instructing two way data exchange?

Here's my take on it.

[andycaps]

Re: Instructing two way data exchange?

Stan,

You have just achieved what I have been trying to accomplish for days in just a few moments, I think the form view is a good idea but I think for �speed� of price setting I may stick with the browse style but your example is fantastic � the price is automatically sent to the products table also.

I shall study your example in fine details and extend my knowledge by learning how you made this � this is really excellent support Stan, I am really grateful thank you�

Andy

[Tim Kiebert]

Re: Instructing two way data exchange?

I figured you would get plenty of help with the mechanics of how to set the logical fields as you asked so I figured I would offer a slightly different data structure: one that eliminates the multiple price fields. I am not saying it is right or better just different. (Well, actually I would prefer it this way) You can set however many prices you need for each vendor-product combo and then choose which price to be the current one for that combo. It may not suit, however, the way you want to display your data.

[Tom Cone Jr]

Re: Instructing two way data exchange?

Tim, I agree. When I see repeating patterns in the structure of a table I begin to think about using a child table, linked one to many. It's more flexible and much easier to maintain when, for example, the customer says "Oh, by the way, we'd like to have 5 different price options instead of only 4". -- tom

[Stan Mathews]

Re: Instructing two way data exchange?

Stan,

You have just achieved what I have been trying to accomplish for days in just a few moments, I think the form view is a good idea but I think for �speed� of price setting I may stick with the browse style but your example is fantastic � the price is automatically sent to the products table also.

I shall study your example in fine details and extend my knowledge by learning how you made this � this is really excellent support Stan, I am really grateful thank you�

Andy

Attached is the same done in a browse.

[MoGrace]

Re: Instructing two way data exchange?

Hi Andy,
I have a bit of an unrelated question. How are your rules for Vendor prices applied? Are they prices dependent upon who is the customer or are they for some other purpose?

[andycaps]

Re: Instructing two way data exchange?

Hi Robin,
The vendor prices table have been set up as an extra table as a single product table would not be suitable.

The issue I faced was there were many suppliers selling the exact same product but over different price bands, which were dependent on how many you buy and how they were procured, i.e. we collect or they deliver or my client collects, thus I needed a table for the vendors and their four different price points.

The help received from Stan enabled me to finish what I set out to do where by I would display the list of products from the Products Table and link the Product ID to the Product ID field in the Vendor Prices table, thus I could then select one of the four prices dependent on a number of factors, it is just not just the �best price� etc.

On top of this there is also buyer/supplier relationships to take in to consideration, thus the cheapest price is not always selected due to overall extra value service I get from the supplier. Meaning I don�t mind paying a higher price for a product if the supplier supports me with annual marketing support!

Having said all this � these are my opinions only � the system I am creating enables a user to set any of their own parameters, which can be a lot different from my own.

Hope this explain it a bit more?

Thanks
Andy

[andycaps]

Re: Instructing two way data exchange?

Hi Stan,

In your Setbox.zip example - how do you replace the 'true/fale' buttons in the browse and set the 'OnChange' programming? Is this possible or not? I can see a way of setting the Xbasic for these four in the browse!
thanks
Andy

[Stan Mathews]

Re: Instructing two way data exchange?

Hi Stan,

In your Setbox.zip example - how do you replace the 'true/fale' buttons in the browse and set the 'OnChange' programming? Is this possible or not? I can see a way of setting the Xbasic for these four in the browse!
thanks
Andy

Sorry, don't understand the question. Do you want to know how I did what I did or how to do something else?

[andycaps]

Re: Instructing two way data exchange?

Hi Stan,
Yes - sorry, i meant how do you replace the buttons with a check box?
Andy

[Stan Mathews]

Re: Instructing two way data exchange?

I don't see a way to do that and a checkbox wouldn't have the onclick event needed to trigger the actions that the button performs. It might be possible to toggle the text on the button from blank to a checkmark character.

[Steve Andrews]

Re: Instructing two way data exchange?

Andy,

Have you considered using one radio button rather than using these four logical fields each with it's own scripts, etc.? If, say, you added a numeric variable to the form called nLevel which could hold values of 1-4, that could be placed on the form as a radio button. This would require no scripting on your part to make sure that only one level was selected. The OnChange script for that field would include the statements:

tbl = table.current()
tbl.P1_Set = (nLevel=1)
tbl.P2_Set = (nLevel=2)
tbl.P3_Set = (nLevel=3)
tbl.P4_Set = (nLevel=4)

which would make your logical fields dependent upon the new form variable.

In a similar manner you could add nLevel to your table and then make the four logical fields calculated fields dependent upon nLevel.

In looking at your table structure and form layout, it just seemed to me that you were reinventing the wheel since some Alpha functionality allowed but one item to be selected from a list. Likewise, you have the choice in radio buttons to display them as checkmarks.

My 2 cents,
Steve