Auto pop textbox on 2nd form with same value as 1st form

[vbaInet]

The OP won't be happy when he/she sees you've called him/her a beginner :O haha! Just kidding. Lets see if the OP can manage this. Cheers Kryst51

 

[Kryst51]

The OP won't be happy when he/she sees you've called him/her a beginner :O haha! Just kidding. Lets see if the OP can manage this. Cheers Kryst51

I think I called the OP "her" at the beginning . I always get a picture in my head of what people look like who I converse with on here, and forget to use gender neutral terms sometimes.

 

[vbaInet]

Oh dear, calling the OP a beginner and now female without checking with him/her. This is heating up lol. Well I better stop writing so we can get back to the problem at hand

 

[Arvin]

LMAO!!!!

You guys are funny!

K ...first ...I am a male...and no hard feelings at all .... overall, my knowledge of access is limited ... I've been using access for 2 yrs and I have created simple apps ....and I will admit ..I go off track and start add pic's and changing fonts before I completly think out the table design.. but I can learn fast!!!! (yawn ...I'm using a cliche again) for instance ... what vbaInet stated ... I do understand the concept, but how in the hell I'm going to apply it is the question/my issue right ? ...

I guess now my question to kryst51 is ... do you want me to try vbaInet's idea ...or continue with I agreed to earlier ...

Thank you for everything ladies...or gents I really appreciate all of your input on this matter

 

[Kryst51]

LMAO!!!!

You guys are funny!

K ...first ...I am a male...and no hard feelings at all .... overall, my knowledge of access is limited ... I've been using access for 2 yrs and I have created simple apps ....and I will admit ..I go off track and start add pic's and changing fonts before I completly think out the table design.. but I can learn fast!!!! (yawn ...I'm using a cliche again) for instance ... what vbaInet stated ... I do understand the concept, but how in the hell I'm going to apply it is the question/my issue right ? ...

I guess now my question to kryst51 is ... do you want me to try vbaInet's idea ...or continue with I agreed to earlier ...

Thank you for everything ladies...or gents I really appreciate all of your input on this matter

IMHO, I would go with the one table with different roles. Either way it will take some work to get you up and running, but the effort in getting it to work will be worth it, and your program will be easier to manage in the long run, also if someone gets promoted it will be easier to fix. Actually with that idea you might want to think of adding an as of date to the employee tables as well.

Something like

pkEmpID
EmpFirstName
EmpLastName
fkRoleID - Number (This will be linked to the "Roles" table)
RoleAsOfDate

This would help keep the history of anything correct, so that records created while the person was not a director stay that way.

 

[Arvin]

Good morning ......

I've starting to work on this already this morning ..... and

Actually with that idea you might want to think of adding an as of date to the employee tables as well.

I will add that...also .... I'm guessing that I would add the "Password" field to the "Users" table?

.....

 

[Kryst51]

Good morning ......

I've starting to work on this already this morning ..... and

I will add that...also .... I'm guessing that I would add the "Password" field to the "Users" table?

.....

If that's your employee info table then yeah, Although you might want to research how other people have done it, as vbaInet brought up a good point about the passwords.

 

[Arvin]

Okay ....

This is what I have done so far .... does this table layout/design seem better?...

Side note .... doing this exercise has already helped me more in understanding "normalization"

Thank you in advance

Arv

 

[Kryst51]

First thought, why a user and an employee table? Isn't every employee at some point going to be a user?

 

[Arvin]

First thought, why a user and an employee table? Isn't every employee at some point going to be a user?

Well .... that was my understanding of what vbaInet had mentioned .... I'm sorry ... I can change it though ... no biggie for me

Pls advise and thank you

 

[Kryst51]

Well .... that was my understanding of what vbaInet had mentioned .... I'm sorry ... I can change it though ... no biggie for me

Pls advise and thank you

Sorry, vbaInet has a problem with you storing the passwords in a table at all, I think. I don't know how you should do it. That was why I suggested you researching on how other people handle password security to gain some idea of your options. But if you are going to put passwords in a different table, you only need the passwordID- fk, EmployeeID-pk and the password itself.

 

[Arvin]

Ahhhhh ...i see ..... So... if I understand this ..then the Roles table would replace the use of having password to access the application? but ... I would I prevent User1 (employee level) from accessing User2s (employee level) information ....

 

[Arvin]

Ahhh shit! ...sorry ...

I guess the DLookup funtion would do that .....

 

[Kryst51]

NO, you still need the password, I just don't know how to do it. For now put it in your employee table. I have a problem with how you have your weekly schedule table is set up.
Your empoyee tole table is set up backward.

The employee role id should be in the employee table, not the other way around.

 

[Kryst51]

Oh, one more thing, any fks should be a number not text.

 

[Kryst51]

Ahhh shit! ...sorry ...

I guess the DLookup funtion would do that .....

Worry about that later, get tables first. put your password in the employee table for now.

 

[Kryst51]

OK, Here is a picture of what I think your relationships should look like so far. Let me know what you think.

 

[Arvin]

Wow ... okay ...

I have removed the "Users" Table
I have created the "Users" Table field in the "Employees" Table
I have changed all fks to "number"

I have a problem with how you have your weekly schedule table is set up

I do to but that is the only way I could think of setting it up ....

OK, Here is a picture of what I think your relationships should look like so far. Let me know what you think.

I think it looks good ...and I noticed the change in the "WeeklySchedule" Table....I get it ..NICE! ...

Do you want me to upload the latest? ....

***just to note I haven't changed the "WeeklySchedule" Table

 

[Kryst51]

Wow ... okay ...

I have removed the "Users" Table
I have created the "Users" Table field in the "Employees" Table
I have changed all fks to "number"



I do to but that is the only way I could think of setting it up ....



I think it looks good ...and I noticed the change in the "WeeklySchedule" Table....I get it ..NICE! ...

Do you want me to upload the latest? ....

***just to note I haven't changed the "WeeklySchedule" Table

Upload once you get the weekly shcedule table fixed how you want it, then we will go from there.

 

[Arvin]

Aighty .....

Here it is