Managing a simple list

[thisboyneedshelp]

Newby here. I have a long list (table) of sequential numbers (column) with information attached (fields). (ex. asset tag numbers with info about each number). Eventually, there may be other tables that form relationships, but for now, not.
These numbers fit into categories (ex. Computers, monitors, etc.) The asset numbers have an "offset". In other words Asset No. 2 has an offset with another asset tag of 2500. So, one item is asset no. 2 then the other item that matches it would be asset no. 2502. This offset changes based on the department. Some departments have a large offset, some no so large.
Question 1: Would it be better to have a single table for all devices or two tables (computers, monitors)?
Question 2: How in the world could I define a form that looks up one asset no (say, computer) and displays it's matching offset device?
I believe once I got to this point, I could handle the queries, forms, etc. It's just getting my head around it all.

[orange]

You may wish to review the tutorial here
http://www.rogersaccesslibrary.com/T...lationship.zip

[thisboyneedshelp]

Thanks. I read the document you provided and it was helpful. I think the main thing I need to get my brain around is entity and attribute with regards to the data for the future as it migrates forward. Thanks again.

[orange]

Go through the tutorial and see how you do. Getting your database structured properly is the key to database long life and ease of use.

I have posted links to some free videos all about data modelling -- search for "Langer" and "orange". There's about 5-7 videos.