I am wondering if this can be done. Spent sometime looking, but I am not finding anything remotely close to an answer. I am working on a db that the user - set up with their last name as a login and password, logs in, goes to a particular layout and automatically inserts their last name or, the (AccountName) in the field of Last Name to find their particular records. This works fine.

The problem is, when the user has the same last name as another. What I wanted to do, if this is possible, is subsitute their (AccountName) with a last name for them which resides in a table. The table contains their (AccountName), last name, first name, etc. In the instance of a last name "Smith" there could be several different people, so it's finding all of them. I don't want the records of other employees to be viewed by just anyone with the same last name. They prefer not to use a number with the last name, so I thought there was a way to cross-reference the (AccountName) within the employee record table that contains the last name to use in the search. Does anyone know if this is possible?

http://www.filemaker.com/help/ScriptsRef-233.html

--sd

Thanks for the tip... I looked at the re-login script, but I must be missing something. No matter what I set the parameters at, still getting the same thing. It's placing the accountName into the last name field instead of going to lookup what the lastname is, and replacing it. Sorry! Been at it for hours now... still not having much luck with it.

A real "account name" for log in must be unique. So I'm wondering how you could have more than one exactly the same. In your Find you'd want an exact Find, with the syntax "==" & Get ( AccountName )

see this thread Link

Thanks to you both! The "==" is what I was missing. The problem was, have people with the same last name, and flagging one of them with a number, like, Smith1. When it was finding the related records for one employee, both Smith, and Smith1 were coming up, so that fixed it! My alternative was to do a 1Smith. So thanks to you both!

Gotta better understanding of it now. Just want to make it as fool proof as possible when 500 people will be using it. Cheers!

Edited March 29, 200817 yr by Guest