Anyone here a Microsoft Access pro? [Plea for help]

[Apoco]

Originally Posted by elderboy02

Ha ha brother. You too have the VBA rage

I graduated with a double major in accounting and finance. I did this because I know I don't have the patience for programming

PS - I ran into another 424 error.

Private Sub chkOther_AfterUpdate()

'Verify Other capability
If [chkOther] = Yes Then
DLookup("[Other]", "tblUserPCE", "UserID = '" & Forms![frmNewUser]![strCurrentUser] & "'") = Yes
Else: [chkOther] = ""
MsgBox "You may not create a user that can authorize Other issues"
End If

End Sub

If the DLookup returns "No" then there is no error. If the DLookup returns "Yes" then I receive a '424' error.
Posted via Mobile Device

[Noodles]

Originally Posted by Apoco

I graduated with a double major in accounting and finance. I did this because I know I don't have the patience for programming

PS - I ran into another 424 error.

If the DLookup returns "No" then there is no error. If the DLookup returns "Yes" then I receive a '424' error.
Posted via Mobile Device

First question, is Yes a global variable in your application?

What datatype is [Other]? Bit, string/text, integer?

Same question with [Hanlding] and [Production]? What datatype are they?

VB and all it's variant is not too clear between take this value and assign to this variable VS is this value equals to this value?

In your case,

Dlookup() = Yes

Access is trying to interpret the above statement and making a guess that you actually want to assign the result of DLookup to the variable Yes (this is a variable, correct? That's why it's telling you to make a switcherroo to Yes = Dlookup().

With regards application security, you should always have some sort of a security in your application, regardless of who will be using them.

If you need help, feel free to send me a message.

[Apoco]

Originally Posted by Noodles

First question, is Yes a global variable in your application?

What datatype is [Other]? Bit, string/text, integer?

Same question with [Hanlding] and [Production]? What datatype are they?

VB and all it's variant is not too clear between take this value and assign to this variable VS is this value equals to this value?

In your case,

Dlookup() = Yes

Access is trying to interpret the above statement and making a guess that you actually want to assign the result of DLookup to the variable Yes (this is a variable, correct? That's why it's telling you to make a switcherroo to Yes = Dlookup().

With regards application security, you should always have some sort of a security in your application, regardless of who will be using them.

If you need help, feel free to send me a message.

Other, handling, etc. are all checkbox format (they are a Yes/No value).

Crap. What I was stating for the "then" really should have remained as part of the if statement. If (this box is checked) and (the dlookup shows authorization for the user to check that box) then (nothing? is there a way to say continue as usual?) else (error statement & exit sub). It was completely a formatting issue on my end. I've only been using access for about 2 weeks which is why it probably didn't pop out to me.

The security in place is an in-db login and user rights list. Once the user logs in they are tied to their account which is assigned user, superuser, admin, etc.
Posted via Mobile Device

[Noodles]

Originally Posted by Apoco

Other, handling, etc. are all checkbox format (they are a Yes/No value).

Crap. What I was stating for the "then" really should have remained as part of the if statement. If (this box is checked) and (the dlookup shows authorization for the user to check that box) then (nothing? is there a way to say continue as usual?) else (error statement & exit sub). It was completely a formatting issue on my end. I've only been using access for about 2 weeks which is why it probably didn't pop out to me.

The security in place is an in-db login and user rights list. Once the user logs in they are tied to their account which is assigned user, superuser, admin, etc.
Posted via Mobile Device

Should have been ...

If [chkOther] = Yes AND DLookup("[Other]", "tblUserPCE", "UserID = '" & Forms![frmNewUser]![strCurrentUser] & "'") = Yes then
... true statement here ...
Else
... false statement here ...
End If

[jcruse64]

Wish I could help, but haven't really done anything with DLookup in the stuff I built for our lab. I agree Access and VBA can be extremely frustrating at times, but it's still a nice little database program for some applications. Also nice that you can "upgrade" the data to something else like SQL Server when the need finally comes, and hang on to your front end stuff.

I found a pretty decent forum for help at:

http://www.access-programmers.co.uk/forums/index.php