Best way to mark items as sold in bulk as part of pallet?

[lowfatcottagecheese]

Well sort of....
My real point is what exactly is the requirement. Since the ultimate user is the Boss, and there is a middle man -the manager - between you and the Boss, and you don't know precisely what the Boss needs, it's difficult to provide focused advice.

Good point, I'll find out more.

General process seems to be:

Gather Computers-->Identify/Record Attributes-->Assign to Pallet-->Auction-->Sale-->Report

That is the vision, yes.

Did you work through a tutorial I mentioned in post #6?

Not yet, got a 22 month old with us since daycare is closed for the holidays that's a different kind of boss, but I will be working on some of those. Thanks again.

[lowfatcottagecheese]

However, should not save manufacturer and type into tblInventory. In your case, Model is the primary/foreign key. Retrieve manufacturer and type in a query that joins tables. As Micron noted, text as keys is not ideal because they index slower and use more storage.

I guess I'm a bit confused--how would Access know the manufacturer/model/type relationship if it's not all in one table? I'm sure I'll understand more once I get a chance to work through some of the tutorials mentioned.

[June7]

You have the model/manufacturer/type info in tblComputers. Save Model in tblInventory. Build a query that joins these two tables to retrieve related data. This is one reason to use a relational database instead of just a spreadsheet - to eliminate repetitive data.

Many would advocate you have an autonumber field in tblComputers and save that value as foreign key in tblInventory, in which case even the Model would not be saved into tblInventory. The same principle could be applied to the processor info (processor does not need manufacturer and type info?).

[orange]

LFCC,

Here is a draft model for consideration. You can test and adjust with some test data.
Comments welcome. Merry Christmas!

[lowfatcottagecheese]

LFCC,

Here is a draft model for consideration. You can test and adjust with some test data.
Comments welcome. Merry Christmas!

Thank you very much.

[lowfatcottagecheese]

This is one reason to use a relational database instead of just a spreadsheet - to eliminate repetitive data.

I think once I go through some tutorials and whatnot I'll understand better, I think I'm stuck in a "spreadsheet mindset". Thanks for all the help.

[ssanfu]

PMFJI,

I see you have some PK fields as text and some tables do not have a PK field.
I have a PK field in virtually every table. In my tables, PK fields are always autonumbers.

Sooooooo, more reading...... (hopefully you will find this useful)


AutoNumber
----------------
Purpose: Use an AutoNumber field to provide a unique value that serves no other purpose than to make each record unique. The most common use for an AutoNumber field is as a primary key..


Microsoft Access Tables: Primary Key Tips and Techniques
Autonumbers--What they are NOT and What They Are