I inherited a legacy table that utilizes "Yes/No" Values with the field names being the actual value that I want. For example. If The field name is RedCar, and the Value is 'Yes' or 'No', depending on whether or not the person has a red car. If the field Name is 'BlueCar', then the value of the field is 'No' or 'Yes', depending on if they have a blue car. I don't want to get into the issues of converting this table into something meaningful, simply because the solution I need for the problem is to be implemented soon. I can spend all of the time in the world that I'd like on redesigning the legacy tables. Philosophical issues aside, here's what I need to do with the 'RedCar=Yes' information. This information needs to go into another table (programmatically, obviously) that utilizes the following: CarType = RedCar, or CarType = BlueCar.
As far as simple SQL goes, I was thinking some combination of an update and Make table query, but I can't seem to get the logic right, and I don't know why. Hell, even if I could convert those values into a temporary intermediate table, it would help greatly. I was also thinking about VBA, but the language itself is new to me, as in I have less than 5 hours practical experience with it. (I do have the O'Reilly VB and VBA in a nutshell, as well as the "Access Hacks" book by O'Reilly.
Any ideas would be greatly appreciated...
As far as simple SQL goes, I was thinking some combination of an update and Make table query, but I can't seem to get the logic right, and I don't know why. Hell, even if I could convert those values into a temporary intermediate table, it would help greatly. I was also thinking about VBA, but the language itself is new to me, as in I have less than 5 hours practical experience with it. (I do have the O'Reilly VB and VBA in a nutshell, as well as the "Access Hacks" book by O'Reilly.
Any ideas would be greatly appreciated...