jgottlieb
New Member
- Joined
- Jun 27, 2022
- Messages
- 6
- Office Version
- 365
- 2021
- 2019
- 2016
- 2013
- 2010
- Platform
- Windows
I have a tool that drops data into ALM as a named table. These names are in the format of "bvtbl_<GUID>". For example, I have one called, "bvtbl_b67bef2f_d120_4c9b_a6ed_bf0bc2c9e6b2".
When I was writing VBA code to get the row count, it could not find the table. I checked the Table Design ribbon, the name was correct. I checked the name manager, the name was correct.
I ran code to get all the named tables and I found the following:
bvtbl_b67bef2f_d120_4c9b_a6ed_bf0bc2c9e6b2 - My named table (Set by the tool that does the data extraction to Excel)
bvtbl_b67bef2f-d120-4c9b-a6ed-bf0bc2c9e6b2 - reported by the script
Note the changes of underscores to dashes (except the first one).
Is there some explanation for this or how I could have predicted this? This was not what I expected Excel to do.
I'm on Excel 365 v2411 Build 16.0.18227.20082 (64-bit) if that helps.
---
As a workaround, I can grab the name of the table on the sheet as I only have one named table per sheet.
Thanks.
When I was writing VBA code to get the row count, it could not find the table. I checked the Table Design ribbon, the name was correct. I checked the name manager, the name was correct.
I ran code to get all the named tables and I found the following:
bvtbl_b67bef2f_d120_4c9b_a6ed_bf0bc2c9e6b2 - My named table (Set by the tool that does the data extraction to Excel)
bvtbl_b67bef2f-d120-4c9b-a6ed-bf0bc2c9e6b2 - reported by the script
Note the changes of underscores to dashes (except the first one).
Is there some explanation for this or how I could have predicted this? This was not what I expected Excel to do.
I'm on Excel 365 v2411 Build 16.0.18227.20082 (64-bit) if that helps.
---
As a workaround, I can grab the name of the table on the sheet as I only have one named table per sheet.
Thanks.