mrhooper Posted October 26, 2007 Posted October 26, 2007 (edited) I am trying to calculate a specific class to a client base. For example, I have customerA, CustomerB, and CustomerC. The type of client needs to be assigned as either, Mens, Womens, or Misc. I set my Calculation to be Case(ClientName= "CustomerA"; "Mens; ClientName= "CustomerB"; "Womens" ; "Misc" This seems to work fine, but if I have many Customer names, is there an easier way then to type each one as a case. I tried stringing them together as Case(ClientName= "CustomerA" or "CustomerB" or "CustomerB" ; Mens… But this did not seem to work at all. Any suggestions or maybe a different method? Im at a loss. Edited October 26, 2007 by Guest
Lee Smith Posted October 26, 2007 Posted October 26, 2007 (edited) Men, women, and MISC??? Why is it necessary to have Misc? Why the Two fields? Why not one field for names, and one Field to denote the sex (i.e. Male, Female) Also, you might want to have more than one field for the names, (i.e. LastNames, FirstName, Middle Initial or Name) the more you break you date up into fields, the easier it will to use, find, sort, etc. later for reports. If you don't need the Misc, you can shorten the case calculation to Case (not IsEmpty ( CustomerA ) ; "M"; "W") Edited October 26, 2007 by Guest
mrhooper Posted October 27, 2007 Author Posted October 27, 2007 The mens and womens does not refer to their sex. It is the category of magazine that the customer prints. Maybe I worded it wrong. Trying to have it automatically know that when customerA is entered, then it is in the men's magazine category, etc.
bcooney Posted October 27, 2007 Posted October 27, 2007 The best way to go about assigning types to clients is to create a table ClientTypes, that has just an ID and a TypeName field. Create a value list "ClientTypes" which consists of the ID and the Name, but only displays the second field (name). Now you have client types ready to go. If clients have only one type: Create a field in clients, _kF_ClientTypeID to store the ClientTypeID. You can set _kF_ClientTypeID to be a popup menu field using the value list "ClientTypes." If clients can be assigned more than one type, it's a bit more complicated. You'd need a join table that stores the combinations of ClientIDs and ClientTypeIDs. Then, I'd probably put a portal to this join table on the Client form view.
bcooney Posted October 27, 2007 Posted October 27, 2007 (edited) The mens and womens does not refer to their sex. It is the category of magazine that the customer prints. Maybe I worded it wrong. Trying to have it automatically know that when customerA is entered, then it is in the men's magazine category, etc. I'm thinking that you're assigning types to customers (clients) and now creating another form (order) for that customer. Just look back thru the relationships order->client->ClientTypes. Topic_190986.zip Edited October 27, 2007 by Guest added attachment
mrhooper Posted October 30, 2007 Author Posted October 30, 2007 Thank you, that will work perfect for what I am trying. Now if I can only figure out why I volunteered to do this I will be fine. Just about time to call a consultant I think. :(
Recommended Posts
This topic is 6294 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