9tanstaafl9
Well-known Member
- Joined
- Mar 23, 2008
- Messages
- 535
I'm having strange issues with a workbook and I'm wondering if the issues could be caused by some sort of corruption. The reason I'm asking the question is because everywhere I look online it says corrupt files can't be opened, and these open and run just fine, they just do something strange.
The files are all copies of the same master file. They appear to be identical. But on some of the workbooks, refreshing the queries causes some of the formula references to jump down one cell, and on the other workbooks they don't. The formula in question is ='Tab Name'!B2. It references a query that only ever has one line, and B2 is the cell I want. But B3 (a blank cell) is the one I get on half the workbooks. Also, using $ or named ranges has no effect. The $ get ignored and the name range just moves to b3.
I've eliminated all logical sources of the issue: (that I can think of)
The files are all copies of the same master file. They appear to be identical. But on some of the workbooks, refreshing the queries causes some of the formula references to jump down one cell, and on the other workbooks they don't. The formula in question is ='Tab Name'!B2. It references a query that only ever has one line, and B2 is the cell I want. But B3 (a blank cell) is the one I get on half the workbooks. Also, using $ or named ranges has no effect. The $ get ignored and the name range just moves to b3.
I've eliminated all logical sources of the issue: (that I can think of)
- It isn't the computer since the same computer & user has both working and broken files, in the same directory
- It isn't the data we are querying since the broken files always won't work no matter what data you use and the working files always work using that same data.
- They all connect to the same database using the same connection string with the same properties
- The formulas are all the same
- The macros are all the same
- The user has no add ons, and no other workbooks with macros
- All the files worked fine until the 9th of this month.
Last edited: