Re: Can't do Index in Access?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Okay...well without the stupidity of Tom's comment (exactly what are you an
MVP of anyway?), I appreciate your input. I'm trying to learn Access and have
no wish to fit it inside an Excel shaped box, I just want it to work and find
I learn as much from things that don't work as things that do. I figured when
I posed the question it was poorly put, but needed to start somewhere. I will
indeed rethink the entire structure. Thanks for your answer John. It's a
start.

John W. Vinson wrote:
I suspect I'll need to do this in VBA, but I've never programmed in VBA in
Access before, and it seems to be different than Excel.

You might say that... <g>

I have a rather
complicated work*** in Excel that I'm trying to move into Access.

Excel is a spread***. Access is a relational database programming
environment. It is emphatically NOT "Excel on steroids" and requires different
approaches and a different mindset!

I'm stuck
on one piece (I've spent a full day on it now) and I would appreciate any
[quoted text clipped - 6 lines]
been able to find out I'll need to use VBA with If-Then-Else statements. I
have tried over and over again with no success.

It's clear that what you mean by an Index is different than the meaning of the
term in Access. I would guess that you would want a Table with 36 rows, and
use the DateDiff function to find which row of this table should be joined.

It's dificult to explain, but what I need is for what is in "Month Index 1"
to be in a current month textbox, "Month Index 2" in the next month, on down
to Month Index 36 if there's enough months in the probable life of the
vehicle. Next month Month Index 1 will be there, and Month Index 2 will move
down one month, etc.

Assuming you have a table with fields UseMonth (values 1 to 36), Model_Year,
and whatever other values you need, you could use either DLookUp or a Query
joining

DateDiff("m", [SomeDateField], Date())

to the UseMonth to find the appropriate row. Your business logic may be
different so I'm not certain this is what you want!

I need this to look at an Option Button "Frame" with two buttons (2008 and
2009 selections, with option 2008 value of 1 and 2009 value of 2) and a model
[quoted text clipped - 14 lines]
I realize this is a little vague, but I hope someone can help me with this
somehow. I've been working on this form for way too long. Thank you.

You're trying to jam Access into an Excel-shaped box. It won't fit. You'll
need to *rethink the entire structure* of your application if it's as complex
as it appears to be! Trying to treat Access as a flawed implementation of
Excel will just get you massive headaches. I am getting a headache myself just
trying to understand your formula, and I don't understand your business logic,
so I can't really suggest how to start this restructuring.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-modules/200902/1

.

Quantcast