Hi all.
This is a recurring porblem on this forum and the MS Access Modules forum, but I have not found a solution in any threads yet.
I have an A97 db which exports a table to an Excel file on the user's desktop. The program checks whether the file exists, deletes it if so, and then saves a new file every time. There is no possibility of anyone else sharing the file, the user's desktops are not read-only, the program controls the filename and it always includes a .xls extension.
This works for nearly all users, but a small number get the 3027 can't update error when the code hits the TransferSpreadsheet method. I have seen many solutions referring to a Microdoft article about DisabledExtensions etc. at
My understanding is that this refers to A2000 and above, and doesn't apply here. I have tried it as a solution and it does not help.
This is the second problem to come up here. The first was that the PCs in question did not have the Excel ISAM driver registered. When I fixed this, I started getting the 3027 message - I can only assume the two are connected, but this has not helped me yet.
What I don't understand is how this works for most users but not for some. All the PC builds are suposed to be the same - obviously thay are not, but I haven't tracked down the difference yet.
Does anyone have any ideas about what I should try next.
hughesai
This is a recurring porblem on this forum and the MS Access Modules forum, but I have not found a solution in any threads yet.
I have an A97 db which exports a table to an Excel file on the user's desktop. The program checks whether the file exists, deletes it if so, and then saves a new file every time. There is no possibility of anyone else sharing the file, the user's desktops are not read-only, the program controls the filename and it always includes a .xls extension.
This works for nearly all users, but a small number get the 3027 can't update error when the code hits the TransferSpreadsheet method. I have seen many solutions referring to a Microdoft article about DisabledExtensions etc. at
My understanding is that this refers to A2000 and above, and doesn't apply here. I have tried it as a solution and it does not help.
This is the second problem to come up here. The first was that the PCs in question did not have the Excel ISAM driver registered. When I fixed this, I started getting the 3027 message - I can only assume the two are connected, but this has not helped me yet.
What I don't understand is how this works for most users but not for some. All the PC builds are suposed to be the same - obviously thay are not, but I haven't tracked down the difference yet.
Does anyone have any ideas about what I should try next.
hughesai