Hi Jennifer & Elena,
Going forward you should try to avoid as much as possible VBA code in GP customizations, as with Windows 2019 Microsoft doesn't support VBA anymore in GP.
That being said, it is normal to see 2 versions of a custom report in the Customization Maintenance list, one with and one without VBA. When you export the custom reports with VBA to a .package file, the VBA code is included into the exported .package file and will be used to recreate the DYNAMICS.VBA file on a new GP client when you create a new REPORTS.DIC from scratch based on the .package file(s).
When you don't select the export by including the VBA code, then your imported reports into the new REPORTS.DIC may not work as expected, since some of the report fields may rely on calculations that are driven by your VBA code...
HTH.
PS: one of the caveat of REPORTS.DIC is that it can be located in a shared folder on the network to be used by various GP clients, but the DYNAMICS.VBA cannot, and therefore it needs to be put in the local program folder of GP. This makes managing customizations with VBA code sometimes challenging.
