Welcome to SPN

Register and Join the most happening forum of Sikh community & intellectuals from around the world.

Sign Up Now!

Combining Fields

Discussion in 'Information Technology' started by rml, Jul 28, 2006.

  1. rml

    rml
    Expand Collapse
    Guest

    I'm trying to combine 114 fields into on memo field with the following code:

    [Pack] = [Part Number] & vbCrLf & [Description] & vbCrLf & vbCrLf & [Sub
    Quantity 1]

    It works fine but I have 114 fields and it does not work when I try more
    than (I think) 75 fields. What is the restriction or is there a better way
    to do this?

    Thanks.
     
  2. Loading...

    Similar Threads Forum Date
    US Defense Department Hiring Resident Aliens in Medical and Language Fields Business, Lifestyle & Leisure Dec 6, 2008
    Sikh News Women more vulnerable to cancer in Punjab's cotton fields (New Kerala) Breaking News Apr 1, 2008
    Sikh News Women more vulnerable to cancer in Punjab's cotton fields (Calcutta News) Breaking News Apr 1, 2008
    Sikh News Punjab's killing fields (The Times of India) Breaking News Feb 24, 2008
    Sikh News MQM fields 218 candidates in Punjab (The Pakistan Link) Breaking News Feb 1, 2008

  3. Rick B

    Rick B
    Expand Collapse
    Guest

    Why would you do this? It is redundant. You already have all the data
    stored in individual fields, why would you want to store the exact same data
    in another field? It violates normalized relational database rules.

    Also, it is very very rare for a properly-normalized database to have more
    than twenty or thirty fields in a particular table. 114 sounds like way too
    many fields for one table. You might think about your structure and see if
    you can change your tables to be more normalized.

    --
    Rick B



    "rml" <rml@discussions.microsoft.com> wrote in message
    news:0315CD94-39BC-42E4-817A-63C0F4C2C1C7@microsoft.com...
    > I'm trying to combine 114 fields into on memo field with the following
    > code:
    >
    > [Pack] = [Part Number] & vbCrLf & [Description] & vbCrLf & vbCrLf & [Sub
    > Quantity 1]
    >
    > It works fine but I have 114 fields and it does not work when I try more
    > than (I think) 75 fields. What is the restriction or is there a better
    > way
    > to do this?
    >
    > Thanks.
     
  4. Larry Daugherty

    Larry Daugherty
    Expand Collapse
    Guest

    It seems you're going to some work to get away from relational
    concepts in implementation while trying to implement those same
    relational concepts programmatically in a free-form context.

    Since you're trying to manage ordered data, why not just create a new
    table with the part number, description & quantity in each row? Kind
    of sounds like a detail table for orders or something like that.
    There will then be no limit to the number of rows you can have in your
    table. You will also be able to massage your data using the
    relational tools and supplied Access goodies.

    HTH
    --
    -Larry-
    --

    "rml" <rml@discussions.microsoft.com> wrote in message
    news:0315CD94-39BC-42E4-817A-63C0F4C2C1C7@microsoft.com...
    > I'm trying to combine 114 fields into on memo field with the

    following code:
    >
    > [Pack] = [Part Number] & vbCrLf & [Description] & vbCrLf & vbCrLf &

    [Sub
    > Quantity 1]
    >
    > It works fine but I have 114 fields and it does not work when I try

    more
    > than (I think) 75 fields. What is the restriction or is there a

    better way
    > to do this?
    >
    > Thanks.
     

Share This Page