Describe what you mean by "type in" and how your tables are set up. There's any number of ways to do this:
You can place a field next to the button, type the ID number into the field (or select it from a drop down), then click the button to perform a script that uses one of several methods to bring up that records. A script trigger can perform the script when you enter data and exit the field or when you select a value from the value list.
The script can open a new window or custom dialog with an input field where you enter the ID number and then the script continues.
If the layout is a list of asset records, just clicking the row can bring up a detail view of the clicked record in the list.
My tables are setup just like an excel spreadsheet.
I have a column that has out "asset tag" numbers in them and I want to be able to press an button and type in any asset tag # say 1212 and it will show all data for that row of information.
Yes, but where will you type in the infomation after you press that button? Do you want a dialog to appear where you type this in?
And where do you want to see the results?
What you describe might be done without adding any new button or script, but I may be misunderstanding you.
Click the Find button in the status area at the top of the screen.
Enter the asset number in the field for that column in your table
Click the perform find button in the status area at the top of the screen
The results can show up in Form view as they are now. I pretty much just want it to jump to that asset # when I type it in.
Go To Record is not a script step you an use for this purpose as you've discovered.
Define a global field to use for entering the asset number of the record you want to find. I'll call it gAssetNumb.
create this script:
Show Custom Dialog ["Please Enter an Asset Number"] // specify YourTable::gAssetNumb as the input field 1 for this dialog
If [ Get ( LastMessagechoice ) = 1 // user clicked OK ]
Enter Find mode //clear the pause check box
Set Field [Your Table::AssetNumber ; YourTable::gAssetNumb ]
Set Error capture[on]
Perform Find 
Use button set up to perform this script and you have what you request here.
This is probaly a noob question, but I can't just copy and paste your text into my script and edit it, it will only allow me to choose commands
Yep, you have to use the editor to select each script step in turn. You'd have to modify this script to fit your actual field and table occurrence names anyway.
You can copy and paste bits and pieces of this script. Example: you can add the If step to your script, then double click it to open the specify calculation dialog. Then you can copy and paste: Get ( LastMessagechoice ) = 1 // user clicked OK into the dialog.
I have all of that in there and I get the error
"The specified table cannot be found"
Here is what I have for my field/table data
Set Field [Asset Management::Asset ID ; Asset Management::Asset ID::gAssetNumb ]
Is Asset Managment the name of your table?
Try selecting these two fields from their respective lists of fields instead of typing them in. That will avoid any small differences between what you typed in and the actual the names of your table occurrence and field.
Asset ID is the name of the table, the database is asset management, which gets put in there when I choose the asset id table.
Asset ID is the name of the field. Asset management may be the name of the file, but apparently, it is also the name of a table in your database.
What part of the expression is highlighted when you get this error?
Sorry, but that's one table with two fields. The fields are named AssetID and gAssetNumb. The table name is in question given the error message you reported.
The error message: "The specified table cannot be found" is an error message that occurred when you tried to add the set field script step and popped up when you click OK to close the specify Calculation dialog box. Correct?
At that moment, when the error message pops up, some part of that expression will be highlighted to show you what part of the expression triggered the error. I need to know what part of that expresson triggered the error as it looks correct from here, but I can't see the rest of your database design to understand why.