I believe the print preview window's code is NOT something you can modify using VBA. It is something buried in Access itself, or perhaps in Windows as one of their "standard" dialogs. So "Can you create a custom print preview window?" No... but maybe yes if you are willing to work a bit on a workaround. You have to bypass the "standard" print preview window by NOT trying to print through that window, but instead directly interacting with the printer object that would be hidden BEHIND that window.
Office VBA reference topic
docs.microsoft.com
If you know the properties to load to the printer object, which you could "ask" through a "roll your own" type of form, and then directly send to the printer yourself, you would at least know exactly what you asked to be done and could record that.
You would have to have found the specific printer you wanted to use through the Application.Printers collection before you diddle with the printer.
Office VBA reference topic
docs.microsoft.com
Since nobody directly prints in Windows any more, I don't know that you can easily tell that something actually got printed. What happens these days is that you create an entry into the printer queue (a WINDOWS data structure independent of Access) and that entry might be waiting for a while depending on backlog, paper jams, empty paper trays, and other common office printer events. In a big-enough domain environment, it would be possible that your print request would be sent to another system for handling. In that case, the answer of whether you could tell how many times it was actually printed is a qualified "NO." IF you could even see it, which might not be allowed due to Windows security settings, you would have to somehow interact with the printer queue, and that would be an API function, certainly not related to the "preview window" at all.
You could also find other articles in this forum using the SEARCH feature because you are not the first person to have asked this question. Someone might have printed an obscure way to do what you want, but you WILL be stepping outside of Access to do it.