We've recently encountered a potential downfall of using ActiveData. We're pulling data from an excel spreadsheet but recently needed to keep separate versions of the spreadsheet (for different versions of our software).

So our script needs to reference different versions. Example: excel1.xls and excel2.xls.

Because the ActiveData references a specific spreadsheet I believe the best solution would be to use direct ADODB connections to the spreadsheet so I can variable-ize which spreadsheet to use. (the only other option I can think of is to copy every ActiveData asset, which there are many)

But I wanted to see if anyone else had opinions before changing a pile of code to use direct ADODB connections.

It's not possible to put a variable in the File path in ActiveData is it, such as:
"C:\automation\commonfiles\excel" & CurrentVersion & ".xls"

Thanks - Andy