Select Case To Open Separate Forms

[MdHaziq]

Hello Forum,

I am having a problem with using Select Case to differentiate different employees when they log in to their respective section forms.

Can someone help me out this Christmas?

Merry Christmas



Haziq

[Micron]

Your db can't be opened by 2007 due to incompatible features you have used. Suggest you post an older version, or remove those features and re-post, or post the Select Case code to get more responses.

[MdHaziq]

Hello,
Micron

Thanks for the reply in this festive season.

I do not know what is causing the not backward compatible so I take screenshots to explain.

My Select Case does not even work.

What I would like to do is to group the employees based on employees.

Open separate forms based on their Section.

Currently, I have only created Form for [Section] = "Elec".

I hope you can help. If you need any clarification. Ask me.

Thanks, And Merry Christmas

Haziq

[Micron]

Better to copy/paste the sql. Opening zipped images (which aren't very clear anyway) is more work than it needs to be.
I'm going to say Access has no idea what [Section] is on the line Select Case [Section]
You probably should say Me.Section.
For such issues, put a break on a code line and cause the code to be executed as it normally would. Then step through the code (F8) and check the value of references such as variables or form control references. Sometimes mousing over is enough. Sometimes you have to check via the Immediate window by typing a question mark then the reference (e.g. ?[Section]) Using this example, I'd bet you'd get an error message as the reference is ambiguous. There may be other issues, but at this point I see no evidence that [Section] has been properly identified.

[MdHaziq]

It is working!

Thanks a million.

Merry Christmas

[ssanfu]

My thoughts,

In table "tblEmployees", the field names "Password" and "Section" are reserved words - shouldn't be used as object names.
In table "tblDesc", the field name "Memo" is a reserved word - shouldn't be used as an object name.


Why is the relationship between "tblMaster" and "tblDesc" a 1-to-1 relationship?
To me, this is wrong - if truly a 1-to-1, then the fields should be in the same table.

[MdHaziq]

Hello,

Steve

Thanks for looking @ my thread.

I will make the changes. I didn't know I was using reserved keywords. There are too many for me to keep track. I will try to remember them.

The reason why I put in another table is because it refers to the item and the list is long-winded. I will make the changes. Now you told me it is wrong table relationship.

Thanks for the advice. I will make the necessary changes as required.

Merry Christmas

Haziq