Hey there, Mr. Two-Time Excel MVP (@MathieuGuindon) - Question for ya...
I've got an XLTM file that I'm going to move to our Teams site. I know that the "M" part has to go because Excel online doesn't support VBA.
I saved it as an XLTM file, but I'm not getting standard "template" behavior, either. i.e., It simply opens MyFile.xlTm instead of opening MyFile1.xlSm
Any idea how to get it to implement standard template behavior and give me a copy of the template instead of just opening the template?
So far, searches for "Excel template teams" yields things about excel templates and teams templates, but not opening excel templates from Teams.
Seems I have to "Open in SharePoint", then from the SharePoint web site, I have to "Open in App", but even then I'm not getting the proper "template" behavior. I can do the same with my XLTM, but it won't execute the On_Open code.
@FreeMan haven't used templates much - most people don't know what to do with them... I'd send HR a .xltx template and they'd merrily edit the template instead of using it as, you know, a template... IIUC templates need to go in a special folder, and then they show up in file/new. Not sure how that translates in a SharePoint or O365 environment.
I've really liked them. So long as I could get someone to open it by double-clicking in Windows Explorer. I've noticed that my On_open code won't fire if they launch Excel, then File | Open the template.
Dunno. The code was primarily to ensure that each one was named correctly, so I'll handle that for now while I find out if there's a way to make Teams/SP do it for me.
If you double-click myTemplate.xlTx in Windows Explorer, you'll get myTemplate1.xlSx opened up, no matter where it's stored. If you do right-click | Open from WinExp, you'll be editing myTemplate.xlTx
If you open Excel, then File | OpenmyTemplate.xlTx, you're editing the xlTx. I think you have to do File | New | from template or something similar at which point it takes you the default template directory. For my users, they'd then have to navigate to where the template lives to open it from there.
^ Just had a brain wave to figure out the file|new|from template thing...
It seems we have some MS tech support people at our beck and call. I'll submit a help desk ticket and see if they can tell me or kick it straight to MS for an answer.
Most users don't make the difference between "I'm editing the template itself" and "I'm editing a new workbook created off a template", which is why I gave up using templates for anything at all: they just make a copy of the "template" workbook instead
> This resources were edited/created following Rubberduck recomendations (RESX Manager) I'll be working in further standardization (same word -> same translation) and maybe you will receive another pull request later.
@this Thanks for the link, I'll take a look - I'm actually not too worried about dealing with pointers tbh, my plan up till now was to write function wrappers in native assembler so this is definitely a step in the right direction!
@MathieuGuindon FWIW the behavior you get when you select a template extension is that it changes the folder path automatically, which can work against the expectation since I think most typically, we navigate to a folder we want, put in a name, then select the extension then click OK. Since it's the last step before clicking OK, the changing of folder path really messes up the expectation. At least it did for me when I was using templates.
@Greedo OK. I still am not sure how it'll work if the code is ultimately starting from VBA. In Rubberduck's case, it's a WPF dialog that ultimately enters into the VBA codebase, so there's non-basic code in the call stack to handle the End of the world. But if it's originating from VBA, the End could end that stack frame also.... like sawing off the branch you're sitting on.
That said, the WinAPI sends messages to the Excel message loop, and so I think it is Excel that actually invokes the callback parameter of the WM_TIMER message. So if that callback parameter goes straight into the VBE typelib and avoids going through any VBA en-route then perhaps it could work
Not sure if that makes sense... Don't fully understand how RD is invoking stuff yet even with the code you linked
I've been wanting to know how to have spaces be added to for loops without having to go back and add them manually. Code cleanup does this in addition to several other helpful tasks.
VBA Rubberducking
VBA Rubberducking