Combining Fields

#1 (**permalink**) 28-Jul-2006, 08:20 AM

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

[Pack] = [Part Number] & vbCrLf & [Description] & vbCrLf & vbCrLf & [Sub
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/information-technology/11333-combining-fields.html
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11333
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 (**permalink**) 28-Jul-2006, 08:20 AM

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" wrote in message
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11333
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
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11333
> 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.

#3 (**permalink**) 28-Jul-2006, 08:20 AM

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.
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11333

HTH
--
-Larry-
--

"rml" 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:
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11333
>
> [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.