To all. Excel Hyperlinks are tricky because they usually embed the complete path to the target file in the =HYPERLINK() function. Which is useless if you want to move the files around or distribute them. That problem can be solved using a bit of VBA to get the workbook's full path, extracting the directory path and either updating the link cells or making a function for the cell instead. I didn't want to do that 'cos it would only work for Excel users (and not everyone uses Excel).
The method I used gets the "current directory" [ =INFO("DIRECTORY") ] in the cell formula instead. As I pointed out, this will only work if you open the workbook from within Excel using File Open. Each time you open a workbook, the "current directory" will change! So, if you then go back to the hyperlinked workbook, the "current directory" function will get the wrong one. If you double-click the workbook in Windows Explorer, you'll get whatever default directory Excel's set up to use. Which is usually My Documents. The same thing happens if you select from a Recent Files list too.
As the =INFO("DIRECTORY") function only seems to be available in Excel, it seems it was a bit pointless anyway
Recommend you relink in the spreadsheet to the files manually. Tedious, but the info's a lot easier to digest with the links working.
Notes on the Bugs ListThis list may well contain bugs that were AMOS Pro V1.x specific and are fixed in V2.0. I haven't checked as I just wanted to nail down a deliverables criterion. If you know of any of these that have been fixed in V2.0, please let me know and I'll remove them.
I set a cut-off date of end of May (2013!
) just so I can partition up the workload. This batch will all be versioned internally as V2.01x.xxx. Anything reported after that date will just go into the next batch (which will be versioned as V2.02x.xxx internally). And so on. I'd be very surprised if there are not some obscure bugs involving obscure instructions that haven't surfaced yet.
For example, one I just came across in the last couple of weeks is that there's an error in the AMOS Equates file. If I hadn't been testing the Ask Editor and Call Editor instructions for the docs, I doubt it would ever have surfaced! (And just noticed it's in my list but not in the spreadsheet! Mea culpa! Mea maxima culpa!
)
The objective is to get a V2.01 release out in the next six months. We won't get everything fixed by then, but should have something worthwhile releasing.
Note also that the version numbers I'm using internally (in the database that holds all this stuff) is in the format 2.xxx.xxx. This is to give a finer granularity for controlling the fixes for us. But releases I would expect to only use the V2.xx format unless there's any good reason not to. So the user will see V2.01, V2.02, etc.