Maximum length of an If Then line in VBA

[dixie]

Is there a maximum length in VBA of a line containing stuff like the
following:
If password = "1234" or password = "1235" or password = ............... Then

It seems to me that at some stage, I add an extra password onto the end of
the line and it does not work. I assumed it might be 255 characters, but
the line that works is much longer than that.

dixie

[PC Datasheet]

Dixie,

It seems you must have a lot of passwords. Assuming you have a form called
"MyForm" and a field named "MyPassword " to enter a password, consider doing
this:

Build a table called TblPassword and put all your passwords in a field named
Password. Then where you are using the If statement, use this instead:

If DCount("*","Tbl Password","[Password] = '" & Forms!MyForm!My Password & "'")
Then
<<Do whatever, the password that was entered is in the list>>
Else
MsgBox "The Password that was entered is not in the list"
End If
--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
re******@pcdata sheet.com
www.pcdatasheet.com
"dixie" <di****@dogmail .com> wrote in message
news:8j******** ********@nnrp1. ozemail.com.au. ..

Is there a maximum length in VBA of a line containing stuff like the
following:
If password = "1234" or password = "1235" or password = ............... Then

It seems to me that at some stage, I add an extra password onto the end of
the line and it does not work. I assumed it might be 255 characters, but
the line that works is much longer than that.

dixie

[Deano]

dixie wrote:

Is there a maximum length in VBA of a line containing stuff like the
following:
If password = "1234" or password = "1235" or password =
............... Then

It seems to me that at some stage, I add an extra password onto the
end of the line and it does not work. I assumed it might be 255
characters, but the line that works is much longer than that.

dixie

It would be more efficient to use a Select Case construct. That could be
any length you like and alot more readable.

e.g

Select Case password
Case Is = "1234"
'run code here
Case Is = "1235"
'run code here
Case Is = "1236"
'run code here
Case Is = "1237"
'run code here

Case Is = "1238"
'run code here
End Select

[Tom van Stiphout]

On Mon, 19 Jul 2004 07:52:08 +1000, "dixie" <di****@dogmail .com>
wrote:

Unless this is a rare exception (but then you would have pointed that
out in your post), this sounds like very bad application design. If
someone wanted to change his or her password, they would have to ask
you to please do so? Sounds like job security to me.
Rather as was already pointed out, users should be able to maintain
their own password, which you would store (perhaps encrypted) in a
Users table. Administrators should be able to reset passwords.

Alternatively, consider that the user is already logged into Windows,
and you can ask Windows what the current username is
(http://www.mvps.org/access/api/api0008.htm). In most cases no further
password should be necessary; the fact that the user was able to log
into Windows is proof enough that she is who she says she is.

-Tom.

Is there a maximum length in VBA of a line containing stuff like the
following:
If password = "1234" or password = "1235" or password = ............... Then

It seems to me that at some stage, I add an extra password onto the end of
the line and it does not work. I assumed it might be 255 characters, but
the line that works is much longer than that.

dixie

[David W. Fenton]

"dixie" <di****@dogmail .com> wrote in
news:8j******** ********@nnrp1. ozemail.com.au:

Is there a maximum length in VBA of a line containing stuff like
the following:
If password = "1234" or password = "1235" or password =
............... Then

It seems to me that at some stage, I add an extra password onto
the end of the line and it does not work. I assumed it might be
255 characters, but the line that works is much longer than that.

The underscore character ("_") can be used to continue lines:

If password = "1234" _
Or password = "1235" _
Or password = "1236" _
Or password = "1237" _
Or password = "1238" Then

Others have suggested SELECT CASE, but gave you an example that
wasn't terribly efficient. This would be preferable:

Select Case Password
Case "1234", "1235", "1236", "1237", "1238"
[do whatever you do when the password is valid]
Case Else
[do whatever you do when it isn't]
End Select

Of course, to reiterate what others have said, storing passwords in
code is not a very good design.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[dixie]

Tom, what you are suggesting about storing passwords in a table is what I
wanted to do, but I didn't, as I was afraid that someone who could access
the tables could read all the passwords. But, if they can be encrypted,
this would solve that. How do you encrypt passwords held in a table? BTW,
the reason the Windows password is not useable is that there are many
password protected areas with different passwords depending on how much
access a user is granted.

dixie

"Tom van Stiphout" <no************ *@cox.net> wrote in message
news:pu******** *************** *********@4ax.c om...

On Mon, 19 Jul 2004 07:52:08 +1000, "dixie" <di****@dogmail .com>
wrote:

Unless this is a rare exception (but then you would have pointed that
out in your post), this sounds like very bad application design. If
someone wanted to change his or her password, they would have to ask
you to please do so? Sounds like job security to me.
Rather as was already pointed out, users should be able to maintain
their own password, which you would store (perhaps encrypted) in a
Users table. Administrators should be able to reset passwords.

Alternatively, consider that the user is already logged into Windows,
and you can ask Windows what the current username is
(http://www.mvps.org/access/api/api0008.htm). In most cases no further
password should be necessary; the fact that the user was able to log
into Windows is proof enough that she is who she says she is.

-Tom.

Is there a maximum length in VBA of a line containing stuff like the
following:
If password = "1234" or password = "1235" or password = ............... Then
It seems to me that at some stage, I add an extra password onto the end ofthe line and it does not work. I assumed it might be 255 characters, but
the line that works is much longer than that.

dixie

[Reggie]

Dixie, Not sure how to encrypt the data, but if you open the table in design
view, select your password field, and type in Password on the Input Mask
line. Now when someone types in the field an asterisk(*) is displayed
instead. Anyone opening the table will also see an asterisk for the
password (i.e **** for password 1234) .

--
Reggie

----------
"dixie" <di****@dogmail .com> wrote in message
news:jX******** *******@nnrp1.o zemail.com.au.. .

Tom, what you are suggesting about storing passwords in a table is what I
wanted to do, but I didn't, as I was afraid that someone who could access
the tables could read all the passwords. But, if they can be encrypted,
this would solve that. How do you encrypt passwords held in a table? BTW, the reason the Windows password is not useable is that there are many
password protected areas with different passwords depending on how much
access a user is granted.

dixie

"Tom van Stiphout" <no************ *@cox.net> wrote in message
news:pu******** *************** *********@4ax.c om...

On Mon, 19 Jul 2004 07:52:08 +1000, "dixie" <di****@dogmail .com>
wrote:

Unless this is a rare exception (but then you would have pointed that
out in your post), this sounds like very bad application design. If
someone wanted to change his or her password, they would have to ask
you to please do so? Sounds like job security to me.
Rather as was already pointed out, users should be able to maintain
their own password, which you would store (perhaps encrypted) in a
Users table. Administrators should be able to reset passwords.

Alternatively, consider that the user is already logged into Windows,
and you can ask Windows what the current username is
(http://www.mvps.org/access/api/api0008.htm). In most cases no further
password should be necessary; the fact that the user was able to log
into Windows is proof enough that she is who she says she is.

-Tom.

Is there a maximum length in VBA of a line containing stuff like the
following:
If password = "1234" or password = "1235" or password = ............... Then
It seems to me that at some stage, I add an extra password onto the end ofthe line and it does not work. I assumed it might be 255 characters, butthe line that works is much longer than that.

dixie

[dixie]

Dear PC Datasheet
I tried your code and it worked fine. What I would like to do is to have
only one password form that generically does all instances of passwords. To
do this, I will have a different field in tblPasswords for each instance of
needing to use a password (20 in all). This means that I need to pass a
different fieldname as the [Password] (domain) part for each use of the
password form so that it can choose the correct set of passwords. I can
pass a field name to a text box on the password form with OpenArgs when I
open the password form. I have been trying to get the contents of this text
box to sustitute for the [Password] bit in the DCount expression:

DCount("*","Tbl Password","[Password] = '" & Forms!MyForm!My Password & "'")

So far no luck. Can this be done or is it too difficult?

dixie

"PC Datasheet" <no****@nospam. spam> wrote in message
news:5x******** ********@newsre ad2.news.atl.ea rthlink.net...

Dixie,

It seems you must have a lot of passwords. Assuming you have a form called
"MyForm" and a field named "MyPassword " to enter a password, consider doing this:

Build a table called TblPassword and put all your passwords in a field named Password. Then where you are using the If statement, use this instead:

If DCount("*","Tbl Password","[Password] = '" & Forms!MyForm!My Password & "'") Then
<<Do whatever, the password that was entered is in the list>>
Else
MsgBox "The Password that was entered is not in the list"
End If
--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
re******@pcdata sheet.com
www.pcdatasheet.com

[Bob Quintal]

"dixie" <di****@dogmail .com> wrote in
news:2Y******** *******@nnrp1.o zemail.com.au:

Dear PC Datasheet
I tried your code and it worked fine. What I would like to do
is to have only one password form that generically does all
instances of passwords. To do this, I will have a different
field in tblPasswords for each instance of needing to use a
password (20 in all). This means that I need to pass a
different fieldname as the [Password] (domain) part for each
use of the password form so that it can choose the correct set
of passwords. I can pass a field name to a text box on the
password form with OpenArgs when I open the password form. I
have been trying to get the contents of this text box to
sustitute for the [Password] bit in the DCount expression:

DCount("*","Tbl Password","[Password] = '" &
Forms!MyForm!My Password & "'")

So far no luck. Can this be done or is it too difficult?

dixie

Yes it can be done. But a better way is to create a two column
password table. Column 1 is the instance of passwords to use.
Column2 is the passwords: so modify your code above

DCount("*",tblP assword","Passw ord = '" &
Forms!MyForm!My Password & "' AND Instance = '" &
me.openargs & "'"

Bob Quintal

PA is y I modified my email address

[dixie]

Great work Bob, that basically does what I need it to. I have however just
run into another problem which is to make the generic password form open the
correct form according to what password is put into it. I have made a field
called fName in tblPasswords which actually has the name of the form I want
to open and I am trying to use that to open the correct form from the
password form.

I am however having problems making that work. If I can't get it to work, I
am going to have to go back to a different form for each instance of
password

I guess I could do some form of Case structure in the password form that
opens the right form according to what is in Me.OpenArgs, but then I am
using hard coded names in the form.

Can you suggest any other way that it can be done without reverting to a
large Case 1, Case 2, Case 3 structure?

Thankyour for your help.
dixie

"Bob Quintal" <rq******@sPAmp atico.ca> wrote in message
news:Xn******** **************@ 66.150.105.50.. .

"dixie" <di****@dogmail .com> wrote in
news:2Y******** *******@nnrp1.o zemail.com.au:

Dear PC Datasheet
I tried your code and it worked fine. What I would like to do
is to have only one password form that generically does all
instances of passwords. To do this, I will have a different
field in tblPasswords for each instance of needing to use a
password (20 in all). This means that I need to pass a
different fieldname as the [Password] (domain) part for each
use of the password form so that it can choose the correct set
of passwords. I can pass a field name to a text box on the
password form with OpenArgs when I open the password form. I
have been trying to get the contents of this text box to
sustitute for the [Password] bit in the DCount expression:

DCount("*","Tbl Password","[Password] = '" &
Forms!MyForm!My Password & "'")

So far no luck. Can this be done or is it too difficult?

dixie

Yes it can be done. But a better way is to create a two column
password table. Column 1 is the instance of passwords to use.
Column2 is the passwords: so modify your code above

DCount("*",tblP assword","Passw ord = '" &
Forms!MyForm!My Password & "' AND Instance = '" &
me.openargs & "'"

Bob Quintal

PA is y I modified my email address