>>>>>>>>1. You should be able to change that file name and chose a place for backup. (just click on Add button to specify your own name)
>>>>>>>>
>>>>>>>>2. This name essentially means nothing (e.g. it's not important).
>>>>>>>>
>>>>>>>>Generate the script from SSMS and look at it and compare with the BOL syntax.
>>>>>>>
>>>>>>>Whenever someone says that "this is not important for you to know" I tend to focus on these things more <bg>.
>>>>>>>
>>>>>>>For some reason I remember either seeing or reading somewhere that the .bak contains all backups created for the database. I was just wondering how (if becomes necessary) I can restore this or that specific back.
>>>>>>>
>>>>>>>What is BOL?
>>>>>>>
>>>>>>>Thank you for your help.
>>>>>>
>>>>>>BOL is Books Online and this is the HELP for SQL Server. Everytime you need to understand some command or how to do something, start from reading Books Online (BOL) and only after you read it, you may ask a clarifying question. BOL usually explains everything in great details, say,
>>>>>>
>>>>>>http://msdn.microsoft.com/en-us/library/ms187510.aspx
>>>>>
>>>>>Thank you very much!
>>>>
>>>>
>>>>How dare you ask a question before you read the BOL and understand it..... :)
>>>
>>>I thought it was a reasonable suggestion, at least reading it and trying to understand it (shrug).
>>
>>It wasn't worded as a suggestion, but as an order.... if you need to understand a command, read the BOL and only after that may you ask a question...
>
>Fair enough. I didn't take it that way but can see how someone might.
>
>I do like it better when there's a sense that the person who asks a question here has tried to solve it on their own first and then comes here when they're stuck. It shouldn't be a first resort when the answer is readily available in the documentation. JOMO....

then that would apply to about 80% of the questions asked here which could have been answered by a 30 second bing search...