sandra312,
Jell may well be correct about Access being the better platform for such an application but the truth is that the learning curve for Access is very steep indeed. It's adopters often use obscure and arcane language which makes the whole process even more difficult. You can get help here on EE on Access but if you don't speak their language it's a waste of time. Personally I had a very poor experience in the help on Access here on EE. However that was a while ago and perhaps the Access experts are now more empathetic.
A few questions and observations:
1. Meantime I need to be clear how you are going to use your workbook. When a week's worth of schedules have been completed, do you re-use Monday's worksheet?
2. I would strongly recommend you not to use the Print-preview mode as the normal mode of use. The column and row headers become unreadable. Apart from that you have had to use unnecessarily large point sizes.
3. To convert your whole workbook into a database with a Userform interface can be done but it would take, most probably, about 1000 lines of code to do it. I have recently written a very similar application for reception desk staff at a police station. It is not a trivial project and certainly not a 'code snippet' solution. There is also the likelihood that not all the cells would be visible without scrolling the UserForm - much as at present in that not all the cells are visible at any one moment.
4. For the moment I believe Jell's suggestion to keep with what you've got is good advice. Don't bother with Combo boxes - Data Validation is much easier - with dynamic ranges of course.
Converting what you have to a UserForm/Database in Excel goes far beyond the scope of questions on Experts-Exchange, and would need to be on a commercial basis. Meantime let's deal with the suggestions made by Jell.
a. Dynamic ranges:
Define named range SCRUBSTAFFLIST as
=OFFSET('Validation Lists'!$E$2,0,0,COUNTA('Va
All the other named ranges used in Data Validation dropdown lists need to be re-defined in the same manner.
That will allow you to add names to the lists and for the new names to be added to the Data Validation dropdown lists automatically. Personally I would just add the names to the lists as and when required directly into the lists themselves.
b. I've run out of time, right now, to do the VBA sorting routines. I'll deal with them later today - if Jell hasn't already dealt with it.
Hope that helps.
Patrick
Main Topics
Browse All Topics





by: jellPosted on 2008-02-25 at 01:39:44ID: 20973898
Hi,
I just want to manage your expectations here:
(1) Trying to solution this in Excel is going to be difficult. Whilst possible, I would strongly urge you against it given your inexperience with VBA. Access would be an easier platform.
(2) It is unlikely that an expert will provide a full solution for you. You are only likely to get advice and VBA code examples in response to more specific questions.
If you decide to continue down the Excel route then I can provide the following advice.
(a) Combo-boxes are not absolutely necessary in my opinion, looking at your setup. Instead, I would continue to use validation lists, but make then refer to dynamic named ranges, rather than fixed ranges. This way, when you add to a list, it will automatically appear in the validation list.
(b) To update the validation lists, I would consider building a VBA form to do this. A combo box to allow selection of the list name, and a text box to allow entry of the new data. Your VBA behind the form should simply access the relevant named range; add an entry to the bottom; and re-sort the list.
Jell