Creating a scheduling database for Microsft Access
Since I started taking programming classes I thought I might help out the small catering company I work at with creating a scheduling app in Microsoft Access since that's what the manager is most used to. I don't have much experience in Access but I thought I'd give it a go.
So basically, employees are scheduled by time blocks which go from Monday-Saturday and are two hours a piece from 6 am to 10 pm. I want to make it so employees enter in the time blocks they're available or unavailable (I'll try a version for each one and see which is more convenient) at for that week and a program will determine which time blocks will be assigned so each employee gets a relatively fair amount of hours each work. I already got a friend more adept at coding taking care of that last part, I just need to create the section that has the employees input their schedules.
To do this, I created the table Employee with attributes Emp_ID, First_Name, Middle_Initial, Last_Name, and Role.
I created a second table Time_Block with an autonumber Time_ID, Weekday, and Time for each timeblock through the week.
Then through a form the employee would select each time ID for the timeblock they're available/unavailable and the selections would be saved in a new table called Schedule with an autonumber ID, Emp_ID, and Time_ID.
Finally, I could use a query to display an Employees name and the weekday/time blocks they've chosen which could then be used in a report which could be exported into an excel spreadsheet which my friend would use for their code.
Now here's the problem I've encountered. It's easy just to have an employee input the various time ID's from the Time_Block table but it's not very convenient. Now I have two ways to make this easier but I'm not sure how to implement them. My first idea was to have a combo box with a button and have the combo box be populated with all the available time blocks and the button would be used to select each time block and store it into the Schedule table.
My second idea was to have a subform on the form with each time block having a checkbox and to have the employee check each time block and only have the ones checked be stored in the Schedule database.
Right now I'm leaning towards the latter option but like I said I'm not really sure how to do it after hours of trying to get it to work.
Help would be appreciated, especially if there's an even more convenient way to do this.
ms-access
add a comment |
Since I started taking programming classes I thought I might help out the small catering company I work at with creating a scheduling app in Microsoft Access since that's what the manager is most used to. I don't have much experience in Access but I thought I'd give it a go.
So basically, employees are scheduled by time blocks which go from Monday-Saturday and are two hours a piece from 6 am to 10 pm. I want to make it so employees enter in the time blocks they're available or unavailable (I'll try a version for each one and see which is more convenient) at for that week and a program will determine which time blocks will be assigned so each employee gets a relatively fair amount of hours each work. I already got a friend more adept at coding taking care of that last part, I just need to create the section that has the employees input their schedules.
To do this, I created the table Employee with attributes Emp_ID, First_Name, Middle_Initial, Last_Name, and Role.
I created a second table Time_Block with an autonumber Time_ID, Weekday, and Time for each timeblock through the week.
Then through a form the employee would select each time ID for the timeblock they're available/unavailable and the selections would be saved in a new table called Schedule with an autonumber ID, Emp_ID, and Time_ID.
Finally, I could use a query to display an Employees name and the weekday/time blocks they've chosen which could then be used in a report which could be exported into an excel spreadsheet which my friend would use for their code.
Now here's the problem I've encountered. It's easy just to have an employee input the various time ID's from the Time_Block table but it's not very convenient. Now I have two ways to make this easier but I'm not sure how to implement them. My first idea was to have a combo box with a button and have the combo box be populated with all the available time blocks and the button would be used to select each time block and store it into the Schedule table.
My second idea was to have a subform on the form with each time block having a checkbox and to have the employee check each time block and only have the ones checked be stored in the Schedule database.
Right now I'm leaning towards the latter option but like I said I'm not really sure how to do it after hours of trying to get it to work.
Help would be appreciated, especially if there's an even more convenient way to do this.
ms-access
Welcome to Stack Overflow. Your question is asking for design guidance and will likely generate opinionated answers, but Stack Overflow is for focused questions that likely have a definite solution. Although guidelines exist for good database design (i.e. table normalization), Access otherwise provides a flexible, fully programmable application platform that supports various designs. You and your manager and the existing processes will likely be the best source of design requirements. Please return with more specific questions about implementing the design you choose.
– C Perkins
Nov 12 at 4:03
add a comment |
Since I started taking programming classes I thought I might help out the small catering company I work at with creating a scheduling app in Microsoft Access since that's what the manager is most used to. I don't have much experience in Access but I thought I'd give it a go.
So basically, employees are scheduled by time blocks which go from Monday-Saturday and are two hours a piece from 6 am to 10 pm. I want to make it so employees enter in the time blocks they're available or unavailable (I'll try a version for each one and see which is more convenient) at for that week and a program will determine which time blocks will be assigned so each employee gets a relatively fair amount of hours each work. I already got a friend more adept at coding taking care of that last part, I just need to create the section that has the employees input their schedules.
To do this, I created the table Employee with attributes Emp_ID, First_Name, Middle_Initial, Last_Name, and Role.
I created a second table Time_Block with an autonumber Time_ID, Weekday, and Time for each timeblock through the week.
Then through a form the employee would select each time ID for the timeblock they're available/unavailable and the selections would be saved in a new table called Schedule with an autonumber ID, Emp_ID, and Time_ID.
Finally, I could use a query to display an Employees name and the weekday/time blocks they've chosen which could then be used in a report which could be exported into an excel spreadsheet which my friend would use for their code.
Now here's the problem I've encountered. It's easy just to have an employee input the various time ID's from the Time_Block table but it's not very convenient. Now I have two ways to make this easier but I'm not sure how to implement them. My first idea was to have a combo box with a button and have the combo box be populated with all the available time blocks and the button would be used to select each time block and store it into the Schedule table.
My second idea was to have a subform on the form with each time block having a checkbox and to have the employee check each time block and only have the ones checked be stored in the Schedule database.
Right now I'm leaning towards the latter option but like I said I'm not really sure how to do it after hours of trying to get it to work.
Help would be appreciated, especially if there's an even more convenient way to do this.
ms-access
Since I started taking programming classes I thought I might help out the small catering company I work at with creating a scheduling app in Microsoft Access since that's what the manager is most used to. I don't have much experience in Access but I thought I'd give it a go.
So basically, employees are scheduled by time blocks which go from Monday-Saturday and are two hours a piece from 6 am to 10 pm. I want to make it so employees enter in the time blocks they're available or unavailable (I'll try a version for each one and see which is more convenient) at for that week and a program will determine which time blocks will be assigned so each employee gets a relatively fair amount of hours each work. I already got a friend more adept at coding taking care of that last part, I just need to create the section that has the employees input their schedules.
To do this, I created the table Employee with attributes Emp_ID, First_Name, Middle_Initial, Last_Name, and Role.
I created a second table Time_Block with an autonumber Time_ID, Weekday, and Time for each timeblock through the week.
Then through a form the employee would select each time ID for the timeblock they're available/unavailable and the selections would be saved in a new table called Schedule with an autonumber ID, Emp_ID, and Time_ID.
Finally, I could use a query to display an Employees name and the weekday/time blocks they've chosen which could then be used in a report which could be exported into an excel spreadsheet which my friend would use for their code.
Now here's the problem I've encountered. It's easy just to have an employee input the various time ID's from the Time_Block table but it's not very convenient. Now I have two ways to make this easier but I'm not sure how to implement them. My first idea was to have a combo box with a button and have the combo box be populated with all the available time blocks and the button would be used to select each time block and store it into the Schedule table.
My second idea was to have a subform on the form with each time block having a checkbox and to have the employee check each time block and only have the ones checked be stored in the Schedule database.
Right now I'm leaning towards the latter option but like I said I'm not really sure how to do it after hours of trying to get it to work.
Help would be appreciated, especially if there's an even more convenient way to do this.
ms-access
ms-access
asked Nov 12 at 1:22
Scud
1
1
Welcome to Stack Overflow. Your question is asking for design guidance and will likely generate opinionated answers, but Stack Overflow is for focused questions that likely have a definite solution. Although guidelines exist for good database design (i.e. table normalization), Access otherwise provides a flexible, fully programmable application platform that supports various designs. You and your manager and the existing processes will likely be the best source of design requirements. Please return with more specific questions about implementing the design you choose.
– C Perkins
Nov 12 at 4:03
add a comment |
Welcome to Stack Overflow. Your question is asking for design guidance and will likely generate opinionated answers, but Stack Overflow is for focused questions that likely have a definite solution. Although guidelines exist for good database design (i.e. table normalization), Access otherwise provides a flexible, fully programmable application platform that supports various designs. You and your manager and the existing processes will likely be the best source of design requirements. Please return with more specific questions about implementing the design you choose.
– C Perkins
Nov 12 at 4:03
Welcome to Stack Overflow. Your question is asking for design guidance and will likely generate opinionated answers, but Stack Overflow is for focused questions that likely have a definite solution. Although guidelines exist for good database design (i.e. table normalization), Access otherwise provides a flexible, fully programmable application platform that supports various designs. You and your manager and the existing processes will likely be the best source of design requirements. Please return with more specific questions about implementing the design you choose.
– C Perkins
Nov 12 at 4:03
Welcome to Stack Overflow. Your question is asking for design guidance and will likely generate opinionated answers, but Stack Overflow is for focused questions that likely have a definite solution. Although guidelines exist for good database design (i.e. table normalization), Access otherwise provides a flexible, fully programmable application platform that supports various designs. You and your manager and the existing processes will likely be the best source of design requirements. Please return with more specific questions about implementing the design you choose.
– C Perkins
Nov 12 at 4:03
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53254900%2fcreating-a-scheduling-database-for-microsft-access%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53254900%2fcreating-a-scheduling-database-for-microsft-access%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Welcome to Stack Overflow. Your question is asking for design guidance and will likely generate opinionated answers, but Stack Overflow is for focused questions that likely have a definite solution. Although guidelines exist for good database design (i.e. table normalization), Access otherwise provides a flexible, fully programmable application platform that supports various designs. You and your manager and the existing processes will likely be the best source of design requirements. Please return with more specific questions about implementing the design you choose.
– C Perkins
Nov 12 at 4:03