Can't Figure this one out.

I WILL SEND SOMEONE MONEY THROUGH PAYPAL IF THEY CAN SOLVE THIS ONE!

I have a deadline to finish this for a client.

I have a value list for types of vinyl. [color:"purple"](3341, 4512, 664859, ect.)

I Need a calculation to charge different type of labor costs depending on what types of vinyl are selected. [color:"purple"](1.50, 2.50, 3.75, ect)

PROBLEM: The value list will be changed, so i cant very well write the calculation like, [color:"brown"] if ( vinyltype = "3341" , 1.50 , 2.50 )

i cant use that because some day the vinyl type [color:"purple"]"3341" might be deleted and replaced by the client with [color:"purple"]"541201"

So. i tried, [color:"brown"] if ( vinyltype = (ValueListItems(Status(CurrentFileName), "VinylValueList") )

but instead of checking against each vinyl type number. [color:"purple"] (3341, 4512, 664859, ect.)

It ended up checking against one long string of numbers. [color:"purple"] (33414512664859 ect.)

If someone can figure out how to get what i need i will pay them. Promise.

[email protected]

916.203.0670

Since your vinyl types and costs may change over time, I'd recommend adding a Vinyl file, where each record is one vinyl type, with fields for ID number, description, cost, and price. Then it's a simple matter to make the labor price an auto-entered Lookup based on a relationship from Vinyl Type Number to Vinyl ID in the new file. This also has the advantage of allowing the prices to change over time without affecting existing orders.

Ho ender.

That would work. except, i am slightly concerned about multiple files.

the client is new to databases. I would love to build it in 7. but they don't own 7.

Can you think of any way to not make a separate database?

Btw, i am trying your idea now. i am seeing how easy it could be for them. i might be able to sell them on it being a "good idea" to have more data on the computer.

~ Matthew

( A third )

Multiple files are standard in Filemaker. In fact, you need multiple files for anything with a bit of power in it.

The user should not be concerned with how many files are there. You should have a main file. This is the file that the user opens - and the only file he/she needs to know about. Create a folder called 'Support Files" or whatever, and put your additional files in it.

Filemaker will open the related files automatically when needed - and you can open them via scripts as well. In the main file, create a closing script that closes all auxilliary files. As far as the user is concerned, it's a single application.

Ho Matthew!

Without the Vinyl file, you'd need an auto-entered calc with a case statement to choose the labor rate based on the Vinyl Type selected. But if your vinyl types change or the prices change over time, then this would require your to edit the field definition. This is undesireble in multi-user solutions, but may be acceptable in a stand-alone solution.