Populating value lists from more than one field

[Jarvis]

Value lists have the option of being populated with values from specific fields.

Is there a way to allow the value list to consist of values from more than one field?

Can these fields be in different tables?

[bcooney]

1 Create a calc field that concatenates the two fields you want in the value list, ie First Name & " " & LastName.

2 What are you trying to do?

[Jarvis]

Thanks for your quick help.

I am trying to build a list of task operations for my cabinetshop.

I build a variety of different product families.

Each family has a series of tasks and the tasks each have a work station.

When assigning work stations I would like to pull from a common list of work stations.

[bcooney]

To what entity are you "assigning" workstations? What tables do you have defined: Products, ProductFamilies, Tasks, Join table btw ProdFam and Tasks "ProdFamTasks," Workstations, Join table btw Tasks and Workstations, "TaskWork."

[skingjack2]

Hi,

I'm hoping to achieve something similar but encountering problems. This is for the case where an indvidual has more than 1 credit card on file; I've concantenated the required fields (fyi, they are all the pertinent credit card fields for a person). Now, in my purchases table, I would like to be able to select which concantenated credit card data ("CCCD") an individual used to make this purchase. I tried creating a value list using an all customers value list...this however returned the CCCD for all the credit cards on file for all records; I'm looking specifically for the CCCD that applies only to the individual purchasing the service. Any thoughts? Hopefully this is enough info to sort out what I may be doing wrong; if not please query me.

Thanks,

Jack

[comment]

Something like this?

CustomerCards.fp7.zip

[skingjack2]

Comment,

Thanks for the quick response & the great example.

It's actually more than what I was expecting =)

Is it possible to simplify this example to just provide strictly the cardID as a drop down menu rather than the both the cardID & customer ID (my thoughts are as the customer info is already on

the sales layout, why the need to to reselect the customerID again?). I'm thinking this is one more step that is not required (or is it?).

If my logic is wrong, than no issue setting

up the DB per your example performing the extra step.

Thanks again,

Jack

[comment]

There is no need to reselect the CustomerID in order to select a card. The card selection uses the value in CustomerID to filter the available cards. It doesn't matter HOW the CustomerID field gets its value.

[bcooney]

I thought it was dangerous, if not illegal, to store cc info...

[LaRetta]

Well, Barbara, I believe you are right. Last time I checked (2 years ago) it was illegal to store CVV2 numbers and credit card numbers can only be stored if encrypted. It is always much safer (and much easier) to use a credit card verisign (or similar) service.

UPDATE: But I'd check the latest laws on it for sure, Jarvis!

Edited January 18, 2009 by Guest
Added update

[LaRetta]

BTW, here are a few good links I've found which discussed the issue on why NOT to store this type of data, illegal or not:

Network Security

Wall Street Journal

[bcooney]

Thanks, LaRetta, thought the issue rang a bell. (See, comment, I'm not losing it, lol!)

[comment]

Yes, I remember that. It was in 1969 and we were drinking Tang.

I wonder what does "concantenated credit card data" mean.

[Lee Smith]

Hi LaRetta,

The OP of this thread was Jarvis. Your reponse is really for skingjack2.

Lee

Edited January 18, 2009 by Guest
Deleted the request for info, as you guys are too quick for me today.

[LaRetta]

Thanks, Lee. :wink2:

[skingjack2]

Comment/LaRetta/bcooney/Lee,

I'll have to investigate your comments re: retention of credit card info; this may differ

due to a different jurisdiction (Canada). This is one for the lawyer... joy, another invoice =)

Also, concantenated credit card data is just a combination of credit card related data (name, number, type etc) into 1 field (much like when one combines first & last name into 1 field). I thought mistakenly I could somehow use this as a

means of figuring out how to remedy my initial problem (selecting appropriate credit card for a transaction).

Jack

[skingjack2]

Comment,

I've been integrating this solution into my own and have noted if I add a credit card "c/c" via the portal in the customers table, the c/c info is added correctly into the card table as well as

showing up as an option on the drop down list in the sales table. However when I chose to use the

recently added credit card from the drop down list, the associated information (c/c type, number) doesn't update correctly. Is this just me or am I possibly missing something?

Jack

[comment]

Hard to tell from here. If it only happens in your file but not in mine, then it's likely a matter of implementation.