R
Robert Nusz
I've developed a Access Front-End application to talk to
Mainframe DB2 tables. All works fine in being able to
view and update data, but there is one issue. When you
access a form or report that links to a DB2 table, the
system flips up a signon screen, that forces the user to
enter a userid and password for access to these
tablespaces. What I would like to do is as the user of my
application signs on, entering Userid and password,
forward this information over to mainframe db2 (under the
covers, hidden to the user) and make an automatic signon
to db2. I would think that this would be done with a
stored procedure or macro, but I'm not quite sure how to
write it. Has anyone in the Ms/Access community already
done this... Is there anyone that can provide a working
model or template to follow. The screen that I get comes
from IBM's DB2 Connect software, which includes the
Dabatase ALias name already prefilled, and requires user
to enter authorized userid and password, which happens to
be the mainframe authorized userid and password as well.
Any suggestions, thoughts, templates, would be greatly
appreciated. Thanks in advance. Robert
Mainframe DB2 tables. All works fine in being able to
view and update data, but there is one issue. When you
access a form or report that links to a DB2 table, the
system flips up a signon screen, that forces the user to
enter a userid and password for access to these
tablespaces. What I would like to do is as the user of my
application signs on, entering Userid and password,
forward this information over to mainframe db2 (under the
covers, hidden to the user) and make an automatic signon
to db2. I would think that this would be done with a
stored procedure or macro, but I'm not quite sure how to
write it. Has anyone in the Ms/Access community already
done this... Is there anyone that can provide a working
model or template to follow. The screen that I get comes
from IBM's DB2 Connect software, which includes the
Dabatase ALias name already prefilled, and requires user
to enter authorized userid and password, which happens to
be the mainframe authorized userid and password as well.
Any suggestions, thoughts, templates, would be greatly
appreciated. Thanks in advance. Robert