VERIFY NOVELL USERNAME AND PASSWORD

[wildsharkuk]

Hi all,

I wish to develop a small access database with the functionality for the user to login using his Novell Username and Password as the information contained will be confidential.

Is there any API calls I can make on the Login Form I design to verify the current logged in user and password. Please note that a user could log in on his machine but may want to use the database from another machine where another user has logged in on the network.

Many thanks for you help on this one as I'm completely stuck.

 

[CWestII]

Since you want them to be able to log in from machines whether they are logged into that machine or not, you have two choices.

1. Use standard Access Security to set up accounts for the database.

Or

2. Add a table to your database that contains the UserIDs and Passwords of the current users. You can start them with a generic password and let them change it to the actual one they want. This would require you to have a login form on which they would type their information. The form would have to be coded to allow them to change their passwords when necessary based on knowing their old password.

 

[wildsharkuk]

Hi CWestII,

Thanks for your response.

Rather than having a table which I would have to maintain, could I verify the User Name & Password against the Novell Network Username and Password - Apologies don't know what it's called in Novell but similar to verification of Windows Username and Password in Windows Active Directory.

Regards

wildsharkuk

 

[hwkranger]

This seems like a little bit odd to me.

Users shouldn't be using each other's machines -- so the regular log in should be fine. You shouldn't need a separate log in for your database, unless you're trying to track who's logged in.

Which then brings to a separate issue, tracking the current user. You should use the Environ() to fetch information about your current user.

Access Workgroups, or a look up table with Logon ID's should suffice for tracking who's in or allowed to access the database.

If you're looking for added security, you should use a SQL server backed, which you can add groups to the allowable access rights -- which is driven from novel domain groups.

I know this is off topic, and doesn't really answer your question, but I hope it helps you.

Randall Vollen
National City Bank Corp.

 

[wildsharkuk]

Hi hwkranger,

Thanks for your input.

I understand what you are saying about users using each others machines.

As stated previously, I don't want to manually recreate and maintain User information that is already stored in Novells equivalent to Active Directory. I don't always work on site and visit external clients so could be out for upto a week sometimes and if an internal user wants to use the database then they would have to wait whilst I'm back in.

I work for the Research team and my colleagues do analysis using SPSS and GIS which tends to tie their machines up for quite some considerable time and would like the flexibility to quickly use someone else's machine to view / amend the client data etc.

Unfortunately due to financial restrictions SQL Server is a no-no.

As stated above, I wish the database to be user friendly and require little maintenance from myself as I'm not always here.

Thanks

wildsharkuk