I was thinking that I needed to have a separate
table for these color values, then do a lookup using the ID field to
retrieve the colors when needed. The color field on Table-A would not be
needed after creating and populating Table-B. Table-A will contain around
1,000 records.
Am I off track
is db?
Thanks for the help.
Brent
-Original Message-
From: Adam Fortuno KOVICK [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 2:13 PM
To: [EMAIL PROTECTED]
Cc: MySQL List
Subject: Re: RE: Newbie question...memo field
Brent,
Maybe but give us more information. I know you moving
> updates?
> Thanks,
>
> Brent
> -Original Message-
> From: Adam Fortuno KOVICK [EMAIL PROTECTED]
> Sent: Friday, August 01, 2003 11:31 AM
> To: [EMAIL PROTECTED]
> Cc: MySQL List
> Subject: Re: Newbie question...memo field
>
>
> Normally I'd say do a s
KOVICK [mailto:[EMAIL PROTECTED]
Sent: Friday, August 01, 2003 11:31 AM
To: [EMAIL PROTECTED]
Cc: MySQL List
Subject: Re: Newbie question...memo field
Normally I'd say do a select...into...from, but I don't think MySQL
supports that. In lew of that, try this:
(1) Create the new table.
CR
]>
Date: Friday, August 1, 2003 11:19 am
Subject: Newbie question...memo field
> Hi all,
>
> I'm fairly new to MySQL and have the following scenario:
>
> The Table-A below was converted from a Filemaker Pro database.
> The color
> field was a value list in the F
Hi all,
I'm fairly new to MySQL and have the following scenario:
The Table-A below was converted from a Filemaker Pro database. The color
field was a value list in the FMP database that converted over as a text
field. The color field contains all the selected values in the value list
(from the
