According to MS, using the Range argument for export with TransferSpreadsheet should cause failure but apparently it does not. Something must have changed in Excel or that guidance has always been bad. Also, HasFieldNames argument should be -1 or 0 (True/False) - if left blank it defaults to false - and has no relevance to export.
Procedure exports to workbook then immediately imports from the same workbook just 1 cell. I think would not get new calc because workbook is not opened. Workbook only recalcs when it is opened. FollowHyperlink can easily open the workbook but then closing it is not so simple. So instead of FollowHyperlink, use Excel automation code between the export and import:
Code:
Dim xl As Excel.Application, wb As Excel.Workbook
Set xl = CreateObject("Excel.Application")
Set wb = xl.Workbooks.Open(CurrentProject.Path & "\" & Me.FileName)
wb.Close True
xl.Quit
Code in workbook not needed.