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
"rml" wrote in message
> I'm trying to combine 114 fields into on memo field with the
Reference:: Sikh Philosophy Network http://www.sikhphilosophy.net/showthread.php?t=11333
> [Pack] = [Part Number] & vbCrLf & [Description] & vbCrLf & vbCrLf &
> Quantity 1]
> It works fine but I have 114 fields and it does not work when I try
> than (I think) 75 fields. What is the restriction or is there a
> to do this?