Customize DSN Login Screen

[bala]

Hi Gurus

The scenario
A MS Access frontend application with Oracle Backend (Linked Tables).
The Database UserID and password is not stored and each user has a
unique UserID and password. There is no common database UserID and
password.

Each time the user logs in, the DSN UserID and Password screen is
displayed. It has three input box and they are
Service Name (it displays the DSN name by
default but editable)
UserID
Password

Requirement:
Is there any way of customizing the DSN login screen which gets
displayed when the user uses the application for the first time?

As mentioned earlier, the application uses linked tables with the
password not stored and there is no common login for the database using
which the UserID/Password can be authenticated in the backend. Also the
UserID/Password is authenticated in the backend and not in the
frontend.

Thanx in advance.

Regards
Bala

[maxhugen]

G'day Bala

Is there any way of customizing the DSN login screen which gets
displayed when the user uses the application for the first time?

First, is it sufficient for the application to know that it's being
used for the first time on a particular pc? In most cases, it may well
be, as generally one user only uses one pc. If that's the case, there
are two things you could do:

1. Create your own 'system' table with a field that gets tagged once a
user has successfully logged into the application.

2. Create a registry entry that does the same as (1) above.

If, however, it really MUST be on a per user basis, you may need to
look at a Windows API call to get the username of the user who has
logged in to the pc, and then record the fact that this user logged in
successfully using the methods above.

HTH

[bala]

Hi Max

Thanx for the response mate. It is appreciated.

It is going to be one user per PC but the requirement is each time the
user logins into the application the user must enter the
UserID/Password.

Generally there would be a single common login to the Database and all
the User Authentication is done in the frontend through custom roles
etc..

In this case the frontend is an open application but the each User has
his/her own backend login UserID/Password.

The frontend application as got linked Oracle tables through DSN. The
password is not stored since each user as got his/her own unique
UserID/Password.

Whenever the user clicks on any Forms/Reports which need to retrieve
Data from the table for the first time (since the user as opened the
Application), the DSN displays it own login screen for the user to
input UserID/Password. This screen acts on its own.

What I need is to control this screen and display customized message if
the User inputs invalid UserID/Password. Also I need to hide the
textbox with DSN name which is also editable.

Is there any API to control the DSN related Login screen?
or
Is there anyway to use a custom login screen and pass on the input
UserID and Password (other than using TransferDatabase) to MS Access
linked tables so that the DSN doesn't throwup its own login screen.

Thanx and have a great day.

Regards
Bala

[Rick Brandt]

"bala" <ba*****@gmail.comwrote in message
news:11**********************@h48g2000cwc.googlegr oups.com...

It is going to be one user per PC but the requirement is each time the
user logins into the application the user must enter the
UserID/Password.

[snip]

The frontend application as got linked Oracle tables through DSN. The
password is not stored since each user as got his/her own unique
UserID/Password.

[snip]

What I need is to control this screen and display customized message if
the User inputs invalid UserID/Password. Also I need to hide the
textbox with DSN name which is also editable.

In my main corporate app I prompt the user at startup for their UserName and
Password required to access our IBM ISeries database (UDB400). I then take
those credentials and use them to attempt a simple passthrough query that
retrieves the system time.

If that succeeds I know the credentials are good and then run a code procedure
that loops through all table links and passthrough queries that go against that
server appending the user name and password to the connect string property.

This way the user is prompted only once per session.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com