You should use an Employee ID and not a name. Employee Names are not always unique and can sometimes change.
But there are several basic approaches (that can be used with Names or IDs)
1) Use this script to get the current user's employee name ( or ID ):
Go to Layout ["Employees" (Employees)]
Enter Find Mode 
Set Field [Employee::AccountName ; Get ( AccountName ) ]
Perform Find 
#Then do one of the following Two steps:
Set Variable [$$EmployeeName ; value: Employee::EmployeeName ]
Set Field [GlobalFields::gEmployeeName ; Value: Employee::EmployeeName ]
Once you have a global field or variable set up with the name or ID. Other navigation scripts can use this value to find the desired records. You can also set up a "lock" expression with them in Manage | Security to control which records are accessible for the current user. If this is of interest, See "Editing record access privileges" in FileMaker Help and check out this particular sub section: "Entering a formula for limiting access on a record-by-record basis" for a description of how to set this up.
But with a global field set up with this value in the appropriate table (Not a "globals" table in this case), You can also use a relationship with portals or Go To Related Records to pull up the correct set of records for a given user.
And you can use a relationship or executeSQL query for the initial query to pull up the data as well. An unstored Calculation field with: Get ( AccountName ) can be used as a match field in relationships to access account specific data.
Thank you, your amazing. It still took me 5 minutes to figure it out an apply it but I'm not done yet and would like to pick your brain some more.
But with a global field set up with this value in the appropriate table (Not a "globals" table in this case), You can also use a relationship with portals or Go To Related Records to pull up the correct set of records for a given user. So if I set up a global variable does it needs a field and what happens when multiple users log on at the same time? If this is not the case then can you explain more how this works.
So if I set up a global variable does it needs a field...
Read what I posted again. This method uses a global FIELD not a variable. Global fields provide each user with their own value specific to them. If User 1 enters or selects "1" i the global field, other users do not see that value and can select their own values in the field. And this does not need to be a global field in every case. I suggest that you read up on portals, how they work and how to set them up.
see: http://help.filemaker.com/app/answers/detail/a_id/3604/kw/global to learn more about how globals work in a hosted database.
ExecuteSQL, will list data from the fields and records referenced in the query all in one field. You can set up a query with tabs and returns to present the user will a table of data much like a kind of "read only" portal. ExecuteSQL can also return the ID's of a set of records in a list. That list of ID's can also be used in a standard FileMaker relationship to match to all of the listed records by their IDs (Primary keys). This approach requires a working understanding of SQL--a query language that can require some effort to learn before you can get it to consistently work for you.
Let me know if you could talk or have time to remote desktop and review my database...
This is not a service that I provide for free and my available time is quite limited. A cheaper alternative might be to research the training resources available to find one best suited for your knowledge level and budget. (Some are free.) A number of people new to Filemaker go that route and return here with specific questions when they hit a question that can't be answered from their training materials.