A family of Microsoft relational database management systems designed for ease of use.
WUPS! That was a mistake, I fear. Data should NOT be stored in table names. If you have one table for Group 1 and another table for Group 2, that's what you're doing! What you describe is reasonable for spreadsheets (a new sheet for each Group) but it's JUST FLAT WRONG for relational databases.
You have not said what your original table is, nor what you will be doing with these "groups" - but I think you need (for this part of the database) just TWO tables: the table you described with two fields, Group and Code, and the other table (whatever it is, I don't know) with the 7-8 character postcodes.
SQL is the language of Queries. A query IS SQL - the query design window is just a handy tool to build SQL, nothing else. Some queries though cannot be built in the grid and you must use the SQL window.
So... let's step back. First off, a point of jargon: in Access, a "DATABASE" is the .mdb or .accdb container file, in which you will have multiple Tables, Forms, Reports, and so on. The phrase "sorting a database" simply doesn't make sense - it's like saying "I'm going to sort my desk."
(looking at my desk maybe that's a bad example..:-{) )
So let's say you have a table of Customers, and one of the fields in this table is Postcode, with values like A1T 3M5
A1A 5G2
B1A 3K5
ok?
If so, create a new Query. Don't add ANY table to it yet. Just go directly into SQL view and you'll see a text window with just one word: "SELECT;"
Edit this text to instead read
SELECT Groups.Group, Customers.Postcode
FROM Customers INNER JOIN Groups
ON Groups.Code = Left(Customers.Postcode, 3);
Now open the query in datasheet view and you should see a column of Groups appropriate for the given Postcodes.
Is that getting to what you want?