xlsm vs. xlsb vs. xltm

xlsm vs. xlsb vs. xltm: are they only three macro enabled extensions?

I have used xltm and xlsm only, do not really know xlsb till recently.

xltm: In most cases, I use xltm, since I think it is template, when people double click and open the file, it opens a copy of the file, not the file itself, so it won't corrupt original file. More importantly, if the file is shared with team members on workplace shared drive, so everyone can open a copy of the file and everyone can use the file on the same time.

xlsm: If there is code to track its own folder path, I use xlsm, for example, I have code to generate an output file and save it in the same folder of this xlsm program, then I will use xlsm. This is not something I can do it via xltm, when I open a copy of xltm file, and I cannot use code to track folder path of original xltm file.

In short, xltm allows multiple people to use the program at the same time, since everyone can open a copy of the file, not the file itself, but it cannot track folder path of original file; xlsm allows users to track folder path of this xlsm file, in case this piece of information is needed for some program, but it is not good for multiple people to run the program at the same time.

I don't know much about xlsb, in what situations I can use xlsb?

Since version 2007, files like xlsx, xlsm are basically a compressed zip file with a renamed file extension. "Inside" are XML files that describe each sheet and all the connections between them, and (in the case of xlsm) a binary file containing the entire VBA project. In the event of a crash, this type of file is somewhat easier to recover from, at least as far as the data is concerned.
A file of the xlsb type is entirely a binary file, as are files of the older xls type. In case of failure, more difficult to recover data. They may run a little faster, and may also be slightly smaller in size than files with an XML structure.

Artik