> Regarding the foreign name identifier:

[MS-VBAL 3.3.5.3](https://docs.microsoft.com/en-us/openspecs/microsoft_general_purpose_programming_languages/ms-vbal/74e5bf34-2a30-420c-9d3b-9341fa4c4c09) does not explicitly restrict against a dot in the identifier. We must this is a possibility. Indeed as I noted in #5881, an Access control actually could contain a dot in its name and such member can appear in the type information API. However that member would be impossible to reference from VBA cod

> Regarding the foreign name identifier:

[MS-VBAL 3.3.5.3](https://docs.microsoft.com/en-us/openspecs/microsoft_general_purpose_programming_languages/ms-vbal/74e5bf34-2a30-420c-9d3b-9341fa4c4c09) does not explicitly restrict against a dot in the identifier. We must treat this as a possibility. Indeed as I noted in #5881, an Access control actually could contain a dot in its name and such member can appear in the type information API. However that member would be impossible to reference from V

> > See #5680
>
> Basically code explorer has some buttons in it to "sync" project. If it's not visible then go through the rubberduck menu and select the option to show code explorer. You can make this show automatically in the RD settings menu.

I find it, thanks.

> > Rubberduck's "Import..." dialog lets you make an ad-hoc multiple-file selection (the VBE's is single-file selections), there isn't any much more to it than that. Code Explorer commands for syncing work more with an "all-or-nothing" approach, exporting all code files to a folder, or importing all code files from a folder. Note that the vanilla VBE's Project Explorer allows importing multiple files at once by dragging source files from Windows Explorer into the toolwindow.

thanks for your p