yafreax Posted March 29, 2004 Posted March 29, 2004 I know that Dynamic Value lists do not work using IWP, but is there any workarounds for this? Here's what we have: We are creating a quick online ordering type system for our customers. We would like to store all customers in one database. The system should have an internal ticketing system. To build this using just a filemaker interface is not a big undertaking. We have a table for customers, a table for items, and a table for orders. The main ordering screen would have a portal that lists the related items specific to the customer that is logged in. This is no problem. However, each item needs to have a pulldown with very specific quantities available per ea. item. For example, Item A may have options for 100, 200, 300 or 400 quantities, while ItemB may have 1000 and 2000 available. These quantities are pre-defined. If we didn't want to use IWP, then it's not a problem, we have one more table that has the ItemID and Quantity, then we have one value list that is dynamic using only related values in the Quantity field from the ItemQnty table. Any suggestions how i can create the same sort of thing through IWP. The only thing i've come up with is re-thinking the structure where our Customer table contains fields for each item they may want to order, and has a value lists per ea. item. This creates somewhat of a nightmare for the internal ticketing part of the system. Version: v7.x Platform: Mac OS X Panther
Newbies leadcrew Posted December 5, 2004 Newbies Posted December 5, 2004 Actually I am having the same problem with the dynamic value list on IWP, can anyone help please?? This is really urgent, I am in real need to find workaround for this issue. Your help is greatly appreciated. Tamer Irdais
stuj1026 Posted December 5, 2004 Posted December 5, 2004 I think they do work. After each choice the user has to hit a buton to do a commit record script step.. Stu
Brunk Posted December 8, 2004 Posted December 8, 2004 Dynamic value lists work differently in IWP than they do in the FMP application. In IWP the key field that is used for the relationship to identify the related values MUST be "committed" before the related values show up in the list. This must be scripted and attached to a button. The problem I am having with IWP value lists in that when the field is entered, the values at the bottom of the list are seen. I wish, of course, for the user to see the values at the top of the list. The value list works properly in the FMP application. Can anyone help?
Recommended Posts
This topic is 7681 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now