type which is only char type not ntext/memo which would make it easier
to order them properly.
>>> [EMAIL PROTECTED] 9/20/2004 9:29:33 AM >>>
With a one-to-many relationship like this, you might want courseID and
courseDescription to be in seperate tables. You could then join ID and
Description to bring back a list of descriptions, grouping the
descriptions together to make it look like one description. Your
Description table would probably have to have some type of ordering
value in it though so you'd know how to construct the descriptions in
the correct order.
----- Original Message -----
From: Lawrence Ng
To: CF-Talk
Sent: Monday, September 20, 2004 10:10 AM
Subject: best approach - appending fields in recordset
hello folks,
I have a situation where the database was designed (limitation in
the
db unfortunately) so that if a user wants to enter a lot of
text/content, they would have to add a new line for every entry that
doesn't fit. Think textarea but only your using multiple "input type
text" =(
so when I pull up the query (which is correct), it displays all the
lines/rows of content for that field entered.
example:
courseID
courseDescription (varchar 80)
so if the description was more than 80 chars, then they would have
to
add another line. if the description was 350 chars, then 5 lines,
etc.
so, how would you approach this where I could append the results
from
the courseDescription field to make it all look like one?
thanks,
Lawrence
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
