Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
The above recordset has a dynamic set of columns (e.g. next run there may be no TICKER column, or some additional column(s) may appear). I need to create a second recordset from this data, of a known and fixed layout and with a larger number of columns, that is the columns in the first recordset are a subset of those in the second. Columns that are in the second recordset but not the first need top be NULL.
It's the dynamic nature of the columnset that gives me the headache. The answer's probably staring me in the proverbial, but my brain isn't seeing it ...
One last go to try and get my head round it - does (for example) TICKER always go into the same column in the target table? Or is the target table something like COL1, COL2, COL3 etc and it goes into any one of those?