Cool.... Not to be too pushy... But, any idea how long that might be??
It appears that it would simply require an SQL change.. I did some testing
and I see that the top SQL statement is generated currently. If the WHERE
statement was changed by adding the Password into the query as in the AFTER
query it will provide only the one that matches and will have no need to
search through the output.
Can you put that into the code or do you see another potential problem with
it?
Thanks again for your help.
Tony
Before:
SELECT DateAdd('d',ma.extension,maExpireDate) AS Expr1,
DateAdd('d',ma.extension,maExpireDate) AS Expr2, sa.AccountID,
sa.AccountType, sa.Password, sa.Login, sa.Shell
FROM MasterAccounts AS ma, SubAccounts AS sa
WHERE (((sa.Login)='myusername') AND ((ma.CustomerID)=[sa].[CustomerID])
AND ((sa.Active)<>0) AND ((ma.Active)<>0)) OR (((sa.Shell)='myusername')
AND ((ma.CustomerID)=[sa].[CustomerID]) AND ((sa.Active)<>0) AND
((ma.Active)<>0));
After:
SELECT DateAdd('d',ma.extension,maExpireDate) AS Expr1,
DateAdd('d',ma.extension,maExpireDate) AS Expr2, sa.AccountID,
sa.AccountType, sa.Password, sa.Login, sa.Shell
FROM MasterAccounts AS ma, SubAccounts AS sa
WHERE (((sa.Login)='myusername') AND ((sa.Password)='mypasswd') AND
((ma.CustomerID)=[sa].[CustomerID]) AND ((sa.Active)<>0) AND
((ma.Active)<>0)) OR (((sa.Shell)='myusername') AND
((ma.CustomerID)=[sa].[CustomerID]) AND ((sa.Active)<>0) AND
((ma.Active)<>0));