Hi sjjs3189.
Welcome to Bytes.com.
As I started to say earlier, but was in a rush, the first approach is unnecessarily clumsy. That said, there are very few occasions where the second is required either, frankly.
Let's start with a link to one of my favourite articles as it can be such an eye-opener for those coming to databases fresh (
Database Normalisation and Table Structures).
Back to your specific issue, do you have over 255 Fields in the data altogether? If so then it's very unlikely you have a very reliable design. Not impossible, but extremely rare for that to make sense. If not then there is no reason I can see why you need to complicate matters by having an extra, separate, table.
With a single table you can design a Form that has the Fields of most interest included as a matter of course, and perhaps a Page (or Tab) Control that contains the rest. Often these will be Controls of Fields that are all empty. That's fine. They'll not take up space that way.
If you're trying to organise your data around Access instead of using what it already provides for you then you should understand that isn't a very good idea. Something generally to be avoided.
If I'm honest, it sounds like you've come to this without a good understanding of what Access already handles for you and thus have over-complicated matters. Not a problem. Easily fixed :-)