I have a button which uses the code below to import an Excel workbook. The database entirely depends on this data so its quite an important function...
We use Wyse terminals which have all been upgraded from Windows 7 to Windows 8.1, and users will only run Access in the 'display' (not sure of the proper name? - the ribbon and navigation window are unavailable by default.) mode on these machines.
-When running in 'display' mode on the Windows 8.1 machines, this button now triggers a message box which says 'Error 3170 - Cannot find installable ISAM' and stops running.
-You can access the 'developer' mode on the Windows 8.1 machines by opening the database via a hyperlink and holding shift - the button does work when you open it this way, but I've been told we're not supposed to do this for some reason and haven't mentioned this to IT, but I don't want my users doing this anyway. I can't understand why this works though.
-The PC I'm building the database on still runs Windows 7 and the button does work on this computer too.
-The same issue occurs with linked tables.
Our computers are locked down by IT, so for example things like the registry editor I have no access to. I've received an email from a colleague who developed another database who said he had to request some sort of patch, but it was a very long process with testing and getting it approved by IT.
Is there a simple solution to this?
__________________________________________________
Bonus Question
I made a workaround where there is a button in the spreadsheet itself which copies the data needed to the clipboard, then in the database another button pastes the data into a table and it loops through everything a ridiculous amount of times to process it and put everything in the correct tables. (A very long process).
This has stopped working for some users and just does nothing when they get to the 'paste' section, but is still fine for others with exactly the same permissions.
Any thoughts?
Code:
DoCmd.TransferSpreadsheet acImport, acSpreadsheetTypeExcel12, "LT_BP_Sched", strFolder & strFile, False, "SAP Input!A50:R250"- LT_BP_Sched is my table - no formatting, just a table to 'paste' into. Other functions sort and format the data after the import because lots of blank fields/random characters are pulled in also.
- strFolder & strFile is the folder and file path.
- 'SAP Input' is the sheet in the workbook.
We use Wyse terminals which have all been upgraded from Windows 7 to Windows 8.1, and users will only run Access in the 'display' (not sure of the proper name? - the ribbon and navigation window are unavailable by default.) mode on these machines.
-When running in 'display' mode on the Windows 8.1 machines, this button now triggers a message box which says 'Error 3170 - Cannot find installable ISAM' and stops running.
-You can access the 'developer' mode on the Windows 8.1 machines by opening the database via a hyperlink and holding shift - the button does work when you open it this way, but I've been told we're not supposed to do this for some reason and haven't mentioned this to IT, but I don't want my users doing this anyway. I can't understand why this works though.
-The PC I'm building the database on still runs Windows 7 and the button does work on this computer too.
-The same issue occurs with linked tables.
Our computers are locked down by IT, so for example things like the registry editor I have no access to. I've received an email from a colleague who developed another database who said he had to request some sort of patch, but it was a very long process with testing and getting it approved by IT.
Is there a simple solution to this?
__________________________________________________
Bonus Question
I made a workaround where there is a button in the spreadsheet itself which copies the data needed to the clipboard, then in the database another button pastes the data into a table and it loops through everything a ridiculous amount of times to process it and put everything in the correct tables. (A very long process).
This has stopped working for some users and just does nothing when they get to the 'paste' section, but is still fine for others with exactly the same permissions.
Any thoughts?
