Password Protecting a Form - Microsoft Tutorial Error

[JVermast]

http://support.microsoft.com/?kbid=209871

I was using this form tutorial to password protect my administrative tools. When I went to run it I received this:

"User defined type not defined" and the line Dim rs As DAO.Recordset was highlighted.

I have little experience with VB and I was wondering if someone here had any idea if it was their code that was wrong, or if it was something I did...

 

[JVermast]

Anyone? This is kind of important

 

[RuralGuy]

Sounds like a reference problem. From any code page go to Tools>References and place a check on Microsoft DAO x.x Object Library (check the latest - mine is 3.6).

OK back to the code page and select Debug>Compile...

 

[ghudson]

Is your db secured? If not then the users will find your password table and do what they want with it. There are simpler ways to password protect the opening of a form or button. Search around for I have posted to simular threads.

 

[Uncle Gizmo]

password protect my administrative tools..

If your administration is only on the data, then an alternative method is to separate your project into the typical "front end" "back end" arrangement give your users access to a general "front end" and have your own "front end" available for your own use. This way the users cannot use your administrative tools because they are not available to them.

 

[JVermast]

If your administration is only on the data, then an alternative method is to separate your project into the typical "front end" "back end" arrangement give your users access to a general "front end" and have your own "front end" available for your own use. This way the users cannot use your administrative tools because they are not available to them.

I don't want administrators access to the backend, just to add values to certain tables that are in the DB.

Currently I have a simple key protect on the DB but if you goto design view you can see the password right there.

Anyone else have ideas on the error?

 

[JVermast]

Sounds like a reference problem. From any code page go to Tools>References and place a check on Microsoft DAO x.x Object Library (check the latest - mine is 3.6).

OK back to the code page and select Debug>Compile...

Thanks!!!!

This worked.

 

[RuralGuy]

You're welcome. Glad I could help.