I dont think it is....

The program in summary.....

I have various categories of data such as employees, various different
materials, tax settings etc. Each category has its own data storage workbook.
I also have a main user interface workbook. The user never manually uses the
data workbooks only the interface workbook. The users data is always saved
from the interface workbook to the seperate data workbooks, so that I can
update the interface workbook at a later date, and the user can simply
overwrite the 'old' interface workbook without the user losing and having to
re-input all their data, which is what would happen if the data was in the
same workbook.

The data workbooks are organised with each 'section' of data on a single
row. For example, in one workbook employee data is recorded, and each
employees details can be considered a seperate section, and hence has its own
row. This is so that I can allow the user to save new employees by inserting
a blank row at the top, and copying data into it each time. Thus the list of
employees and their data gets longer and longer each time the user enter a
new employee. I will also be able to allow editing or removing of individual
sections of data by deleting rows.

Each time the user enters employee details such as name, age, address, phone
etc in the user interface workbook, and clicks the save button, the info is
copied and saved in the employee data workbook for later retrival.

The user must be able to later view any of the data that they have stored.
In this case the data stored for any individual employee. I could simply copy
the relevant row back from the data workbook to the user interface as is, and
yes, the user could see it, but it looks crappy. So where the data is called
back to the user interface, I have laid it out differently on the page to
look better, and thats what is causing so many different lines of code,
because there have to be 33 seperate cells copied instead of a single row.
Hence the age which is in column B on the data workbook is now moved down and
onto column d on my user interface. Each cell in the data storage workbook is
in a different location after bringing it back for presentation. There is a
more user friendly look to the user interface....thats why its the user
interface! lol

Anyway, now I think you might get the idea. If I have to do a three thousand
long 'Select Case' for this then so be it, but I know in my heart that
there's a better and simpler way, but because of lack of experience, I don't
yet know what it is!!

All suggestions are welcome....

"JLGWhiz" wrote:

Just a casual observation, but the problem might be more in the sheet data
layout than in the code structure. If you have to write a case statement
that is that complex, then the data base must have been randomly constructed
without consideration for future data retieval or manipulation. Of course, I
don't know what your company requirements are either, so maybe I am blowing
smoke.