[Access 2007] Runtime Error 3219

Meinthecorner

Registered User.
Local time
Today, 13:06
Joined
Nov 29, 2008
Messages
25
I'm using the basic Password Challenge from this MS Bulletin

http://support.microsoft.com/kb/209871

I have a FE \ BE based database but I'm Getting the error "3219" after the user has pressed submit.

The Password form code is

Code:
If IsNull(Forms!frmPassword!Text0.Value) Then
                 MsgBox "You cannot enter a blank Password. Try again."
                 Me!Text0.SetFocus
            Else
                 MyPassword = Me!Text0.Value
                 DoCmd.Close acForm, "frmPassword"
            End If

The error is not present if I load the form and submit on the backend table. I've never had it before as the database has just been split due to requests from other users to access the database.

Now I'm slowly learning VBA so does anybody have a Solution and a basic explanation as to why it happens?
 
I would guess that it is because you are using .Value (instead of .Text perhaps). I would drop any .Whatever after the name of the control.

-dK
 
Thanks for the reply, replacing the .value to .Text resulted in a different error. And removing it all together resulted in the same 3219 message.
 
Just looked at your link. :rolleyes:

You are doing this in the Northwind database? Or trying this technique in a database of your own?

-dK
 
I robbed the example from Northwind and wedged it into my database. It was all working fine till I split the Database :(
 
Thanks :) To be honest I really don't understand most of that. Ho hum, not to worry, I'll do some more reading to get a better understanding. Thank you for your help.
 
Fixed! I feel like beating my head against the wall as I kind of answered the question in my first post. I moved the password table to the frontend instead of it being linked to the backend and it solved the problems.

Thanks dkinley for your pointers :)
 
:eek: Egads! I didn't even pay attention to the FE/BE bit in the first post. Without looking at that link again, I would opine that the password table does not need to be moved to make it work. I have user tables that are linked and working just fine (although I have a different implementation).

Note, that I would keep working this issue because if a user changes their password and goes to another machine - the new password will no longer work!

However, if this is not a concern - I am glad you found a solution.

-dK
 

Users who are viewing this thread

Back
Top Bottom