Re: error message that says too many fields
- From: "Rick B" <Anonymous>
- Date: Tue, 1 Nov 2005 12:33:54 -0600
Just tell us what you are doing. What tables do you have, and what fields
are in each table? How are the tables related to each other.
For example, a contact management database might have one table that stores
information about people. Another that stores information about Companies.
Another that ties people to the companies for which they work. Another that
stores phone calls made and details about each call. This call table would
be linked to the person you called and that would be further linked to the
company for which they work.
Creating a flat design would put all this in one table, and every single
time you logged a call, you'd also have to put the company data and person
data. A flat design very often leads to duplicate data in your tables.
That is one way to spot a bad design.
Another issue can be including data in your fields. Lets say you want to
track payments made by customers. The customer gives you a check for $500.
$400 is to cover the rent, $50 is to pay a late fee, and $50 is to pay for a
new lock on their front door that they requested. A poorly designed table
might have all the fields for the payment data (customer, date, amount,
etc.) and then would have a field for each type of service being paid (rent,
deposit, late fee, etc.). For most payments, only a few of those fields
would be used. This generally indicates a bad design. Another key here is
that the field names contain data. This is normally wrong. A better way
would be to create a main table for the payment, and a separate table for
details. If the receipt only pays rent, you'll have a record in each table.
If it pays rent and a late fee, you will have one record in your main table
and two in your details table. The details table would have the Rect
Number, the ItemAmount, and the ItemDescription or ItemType. You might even
have a third table to store the valid ItemTypes!
Post back and we will try to help you (unless this message gave you some
ideas).
--
Rick B
"DeannaLynne" <DeannaLynne@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:99CFD51B-67DA-4EEE-AE15-5D79BB8BAD3A@xxxxxxxxxxxxxxxx
> admittedly, I don't know much about access--so I am probably committing
> multiple errors!! It is my boss's idea to use access--I don't know why we
> aren't using a statistical package being that the goal is to do a
> qualitative
> analysis of the data that I am entering (but that is why he makes the big
> bucks, I guess). How can I share my database deisng with you?
>
> "Rick B" wrote:
>
>> First, 75 fields is probably WAY too many.
>>
>> A properly designed database table should have 15 or 20 fields at the
>> most.
>> Are you sure your design is correct? Are you committing "spreadsheet"?
>>
>> You might want to share your database design with us and we will offer
>> some
>> help.
>>
>>
>> --
>> Rick B
>>
>>
>>
>> "DeannaLynne" <DeannaLynne@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:1E2A6D6C-FEA7-4422-B600-00FABE965AD9@xxxxxxxxxxxxxxxx
>> >I am trying to save my table. Each time I do, I get an error message
>> >that
>> > says too many fields defined. Right now I have 75 fields--I thought
>> > the
>> > limit was 255. What is going on?
>>
>>
>>
.
- Prev by Date: Re: error message that says too many fields
- Next by Date: Re: Form Load
- Previous by thread: Re: error message that says too many fields
- Next by thread: Re: error message that says too many fields
- Index(es):
Relevant Pages
|
