trying to make a form for folks to use to put in the information

there are only 2 T-G manufacturers (we will call them OEMs, orig. equip. manufacturers), GE and siemens/westinghouse. each OEM puts out its own form of tech. recommendation (TR).

we have 27 T-G units that must have their statuses on each TR in the database. each of these 27 is either GE or siemens/westinghouse.

i want a form where you enter the OEM and TR # and it only lets you input a status for the units that are from that OEM. i want it to just make it where you can't input any status at all for the units that aren't from that OEM.

is it possible to kinda lockout certain parts of the form based on previous entries on the form or how should i go about this? maybe separate tables, one for GE and one for S/W?

[Edited on May 29, 2009 at 8:54 AM. Reason : clarify]

5/29/2009 8:53:37 AM

5/29/2009 2:56:39 PM

Of course it's possible, but you're better off hiring someone to do it.

5/29/2009 4:11:44 PM

Quick sanity check: How many folks are going to be using the MS Access Database?

In summary, yes it can be done, but there is likely a better solution.

5/29/2009 5:38:41 PM

Use the OEM to filter the TGs before presenting them to the user

5/29/2009 5:53:21 PM

figured out a way to make it work

create one table for each OEM. create a form for each of those tables. create a switchboard where they pick one of the two OEMs and the button they pick opens up the correct form.

only took me all day

5/29/2009 7:14:53 PM

That solution would make most DBA's cry. It's inflexible, but probably doesn't make a difference in your case.

5/29/2009 8:35:49 PM

I'll just ask my question as this topic seems close enough. My boss is a nice guy but can't seem to shake his need to have at least a barebones database up and running on the start up of a new product line we have going, for the 5 or 6 engineers/techs/salesmen that may be using it. I am a complete n00b when it comes Access (2003 if it helps) and to coding/nomenclature for specific programs.

Basically I have 25 to 30 records of previously completed special orders for the product, with about 25 columns each of particular information for the parts/sizes needed on each order. Right now I just have a master excel sheet that someone can look and search easily by whatever they see. I can import the data in on the excel sheet to a table. The queries and relationships are a harder nut to crack and where I get to drooling and staring even after seeing tutorials. Obviously when this sheet grows to 100 to 200+ records it will become harder to search it for particular information.

I'm looking at trying to get a form to have the drop-down boxes for each column information so that a user can choose any of those particular boxes for records that match, and have it filter down each time so it only displays records that match ALL of the user's selected boxes. I know it's attainable, but what can I do to form the correct relationships and/or queries to get this or at least where to start?

6/3/2009 7:15:40 PM

man, i got so damn confused with this shit. i was trying to do about the same thing you're doing.

the guy i'm doing this for had his heart set on a database too, but i explained that it was totally unnecessary and that i didn't think it was a good use of my limited time

so i just put it in a spreadsheet and it only took a couple hours

my advice would be to leave this shit to the pros

6/3/2009 7:20:17 PM

Believe me I want to, our IT dept head is a genius software-wise on multiple platforms but he absolutely despises Access so he's a no go. The 5 or 6 people who actually have it on their computers only pull basic queries and use the forms as a nicely formatted record. Our company is fairly small so there's only a few people who know anything more about Access. I'd literally pay some independent access guru if I knew it could take them just a few hours to set it up.

6/3/2009 7:41:41 PM

send me a PM if you're serious

[Edited on June 3, 2009 at 7:57 PM. Reason : .]

6/3/2009 7:56:52 PM

I can confirm ^ will deliver.

6/3/2009 8:01:53 PM