G
Guest
I'm trying to create a control program to restrict access to a couple of
Access apps. One of the apps has a table with users and passwords, so I'm
using this table as a framework.
The Logon app is pretty simple, displaying a list of apps the user can open
if they get their password right. I'm using a Shell command to open the
chosen app and SendKeys to send the password to the database. I know, it's
ugly, and not 100% secure...
We're in a mixed W2K and WinXP environment. I have a batch file that copies
the most up to date MDE for the Logon app to the users computer, and is
supposed to open it...in W2K it does so fine. But in XP the file is copied
and not opened.
I'm guessing that it might be the Macro security issue, and the use of
Shell...or are there any otehr pitfalls to trying to open a database app from
the command line in XP?
Access apps. One of the apps has a table with users and passwords, so I'm
using this table as a framework.
The Logon app is pretty simple, displaying a list of apps the user can open
if they get their password right. I'm using a Shell command to open the
chosen app and SendKeys to send the password to the database. I know, it's
ugly, and not 100% secure...
We're in a mixed W2K and WinXP environment. I have a batch file that copies
the most up to date MDE for the Logon app to the users computer, and is
supposed to open it...in W2K it does so fine. But in XP the file is copied
and not opened.
I'm guessing that it might be the Macro security issue, and the use of
Shell...or are there any otehr pitfalls to trying to open a database app from
the command line in XP?