Re: help with looking up in a table - all varaibles

From: Cindy (cindy.luffer_at_amec.com)
Date: 03/01/04 

Date: Mon, 1 Mar 2004 05:23:45 -0800

Thank you for answering me again John,

Disclaimer here, I know it is unorthadox to do what i'm
doing in a database, but that is why I am doing it...I
want to see it done. To see how user friendly it'll be.

I have the nominal pipe diameter, this is the size of the
pipe that you would 'refer' to the pipe as, it is what it
measures say, inside....you have 10 inches, 12, 14, 18,
etc, etc. The pipe schedule is what kind of pipe you are
choosing. Schedule ID, will give you an outer diameter of
10.16 and Sch 10S, will give you 10.54 inches. These are
examples, there are many types of schedules.

In my form, the person chooses the nominal diameter and
then the schedule they would like. The answer to this,
the actual pipe size, is used in my next equations on this
form - figuring the velocity of how fast the liquid will
go, for example. Therefore the actual pipe diameter is
important.

Thus far, I have been trying to ask the database to look
up the pipe schedule (floating value, but answered in the
form already),this is the field I want looked up but it
moves and the nominal pipe diameter, this field stays
there but the row you would go to changes depending.

It seems like there would be a simple way?

I am trying to think differently here. I was so proud of
myself for being able to write visual macros in basic and
vlookup tables, but now I am graduating to the access
world, do something my bosses haven't done ;)

Let me know if I'm clear, I can try to explain better if
you wish.

Also, have access programs been written for palm pilots?
Something a guy (or girl) can carry around a plant with
them, figuring stuff out with my forms? Just a thought.

Thanks again,
Cindy
>-----Original Message-----
>On Fri, 27 Feb 2004 06:30:47 -0800, "Cindy"
><anonymous@discussions.microsoft.com> wrote:
>
>>Marchall, I tried that already and it didn't work but
>>thank you...and Marshall, I think you've hit it on, I
can
>>have a separate table depending on pipe schedule,
problem
>>is, the table name will change according to what the
>>selection is for pipe schedule. Can I have a condition
>>for this?
>>
>>Example: Dlookup("[Nominal Pipe]","Form![Pipe
>>Schedule]","[Type of Pipe]"...if my Pipe Schedule is the
>>name of the table and this changes depending on Pipe
>>Schedule name.
>>
>>I really wish I could be more clear but you can't draw
out
>>a table here.
>>
>>I am trying to build a pump calculation program on
access,
>>i know this is crazy, but no one has done this type of
>>program on a data base, and i thought it could be a fun
>>tool.
>>
>>My first column is nominal pipe, second is Type of Pipe -
 
>>both these have to be specified...then the following
>>columns ARE type of pipes, (example sch 10s, ID, etc).
I
>>can perhaps split these each up into a table each? I
>>still have two unknowns for a table look up. I did this
>>SO EASILY with a Vlookup in excel. There is no Vlookup
in
>>Access though.
>
>There is a DLookUp but THAT IS NOT THE PROBLEM.
>
>Excel is a spread***, a good one.
>
>Access is a relational database.
>
>THEY ARE DIFFERENT, and they require different thinking
and a
>different mindset.
>
>I don't know enough about pipe to make any real
suggestions, but I do
>know that you CAN create a normalized table which will do
this
>calculation for you in a simple Query. What you need in
the table is
>the information you need - in two fields, or three
fields, or five, or
>whatever it takes - to identify the data that you want.
You can then
>use a Query with criteria on those fields to find the
record
>containing the information that you want.
>
>Please explain as to a dummy who's never bought pipe what
the options
>are and how they determine the price. 10s and ID means
*absolutely
>nothing* to me, so you'll need to clarify!
>
> John W. Vinson[MVP]
> Come for live chats every Tuesday and Thursday
>http://go.compuserve.com/msdevapps?loc=us&access=public
>.
>