The desire to make a table with that many fields is "almost certainly" caused by
an improper design. What you are trying to represent in a single table most
likely should be distributed among multiple related tables.
What is the data that you are trying to work with?
It is very likely that the data structure you have in mind is not
"normalised". If you would post back with some more details of the
fields you need, with examples, someone will be able to offer some
good advice as to a valid table design.
I know that probably there are many solutions for my
project. The main problem is that i didn't check maximum
fields of the table in access. Now i have tons of invalid
vba code.
That why you should design the Table Structure first and make sure it
satisfies the Relational Database Design Principles before actually
implement it and move on to later stages of the database implemetations
(Queries / Forms /Reports). Even if you can use a temp. work-around, e.g.
breaking into 2 Tables with 1-to1 relationship, there will be other problems
later.
Thus, the only sensible solution is to go back and start with a properly
designed Table Structure.
Sure, Doug. I wasn't relating to SQL Server. I interpreted
Konstantin's question to mean whether in Access he could make a query
with more fields.
- Steve Schapel, Microsoft Access MVP
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.