D
Daniel Tuma
Here's my dilema,
I have a dbase that maintains clock in/out, Vacation and
sick day info which needs to be secure. SQL server back
end, Access 2002 front end. When the whole database was
run in Access I was able to use a simple parameter that
would prompt for a password, then compare it to a password
field in the employee table. Now that I "Upsized" the
dbase I find that SQL doesn't like the Access parameter
method. I tried playing around with a stored procedure and
successfully created a SQL password parameter as follows:
CREATE PROCEDURE PasswordGet (@PasswordGet varchar(50))
AS
SELECT Employees.LName, Employees.FName,
Employees.MI,Employees.Designation,Employees.Department,Emp
loyees.HireDate
FROM dbo.Employees
Where PW = @PasswordGet
My problem is getting the Access front end to prompt for
the password and then pass it to the procedure for
validation. I do not have any VB knowledge so I'm looking
for an Access/SQL answer.
Any Ideas?
Dan Tuma
I have a dbase that maintains clock in/out, Vacation and
sick day info which needs to be secure. SQL server back
end, Access 2002 front end. When the whole database was
run in Access I was able to use a simple parameter that
would prompt for a password, then compare it to a password
field in the employee table. Now that I "Upsized" the
dbase I find that SQL doesn't like the Access parameter
method. I tried playing around with a stored procedure and
successfully created a SQL password parameter as follows:
CREATE PROCEDURE PasswordGet (@PasswordGet varchar(50))
AS
SELECT Employees.LName, Employees.FName,
Employees.MI,Employees.Designation,Employees.Department,Emp
loyees.HireDate
FROM dbo.Employees
Where PW = @PasswordGet
My problem is getting the Access front end to prompt for
the password and then pass it to the procedure for
validation. I do not have any VB knowledge so I'm looking
for an Access/SQL answer.
Any Ideas?
Dan Tuma