This looks exceptional. Code is much cleaner than the editor generated spaghetti and the copypaste code I spliced in there. Protecting and unprotecting just the worksheet seems more sensible.
The macros were done by "recording" and are saved to the worksheet. Buttons were created from the developer tab, controls menu, "insert" dropdown, and are placed in a relatively handy spot on the same worksheet as the whole operation is happening. Unprotecting just the worksheet will be fine. If there is ever a second sheet, it'll be different tools.
A quick question about:
FieldInfo:=Array(Array(1, 1), Array(2, 1), Array(3, 1), Array(4, 1)),
This was recording generated and I'm not sure of its function. This "may" correspond to 4 cells where i input delimated junk data in the first column of the intended array, so the function would work as I recorded it. My concern is that this array should actually be (overall) 3 columns by 10 rows, and that my other similar arrays (and the associated macros) all should be various numbers of columns by 10 rows... but the array statements in the macros all seem to have no logical correlation UNLESS it was defined by which cells had junk data.
Should I edit the array statements up to (10, 1), (the column I intend to paste the csv data)? Should I define the multiple columns of the input array for csv pasting, as well? Will this prevent attempts to paste too many csv values?
Thanks for your help...
|