Error 3027 on XP, but works on Win2K

[option]

Hey guys,

I'm using DAO to add a record to my linked table. When I get to the ".AddNew" part, I get the Error 3027/read-only error. Now, the linked table is not read only since it is an excel spreadsheet, but when I view it via Access as a linked table, it is read only(no editable records/unable to add a record). However...when I open this same DB on my other pc running Win2K, the linked table/spreadsheet is not read only, and the code executes just fine. This wouldn't be a problem if I were the user operating the database everyday, but I'm not and they are using Windows XP (which gets the 3027 error). Any ideas as to why this will work in Win2K and not XP?


Edit- According to http://kbalertz.com/904953/cannot-delete-tables-linked-Excel-workbook-Office-Access-Access.aspx , you can not change or edit and data in a linked spreadsheet using versions of Access greater than Acc2K. Since everyone that has an XP machine here has at least Access 2002 or 2003, this is why they can not run this database and I can (my Win2k machine has Access 2K obviously).

 

[The_Doc_Man]

While I've not tried this (due to lack of need), I have to wonder if something else is going on regarding linked spreadsheets.

If you allow those people to open a "test" Excel workbook kept in the same folder as contains the "true" target, can they update the test workbook?

If yes, then I'll back off and let someone else take a shot at this one.

If no, your problem is Windows Folder permissions. Access will want to update that spreadsheet because it is a table (to Access) and tables must be updateable. If it cannot update the table, it is obviously faulty, right? (To the way Access thinks, anyway...) These other folks can surely have different permissions than yours because after all, you are the developer and they are not developers.

Oh, another possibility. Get someone you trust to try to open the "real" spreadsheet and see if there is some other error. It occurs to me that if there is a big version mismatch between your copy of Excel and their copy of Excel, the linkage might be problematical because of Excel output format differences. I.e. .XLS file was written in version A, Access tries to open it but needs it to be version B (where B > A). And from the Access environment, that conversion is impossible.

 

[option]

My previous edit was a knowledge base article from microsoft (original can be found: http://support.microsoft.com/kb/904953/). It provides a workaround solution, but I've got a different idea which fits my situation and should work. The database that makes the spreadsheet I am linked to is getting its query modified to substitute using DAO in the second database. Here is another article from Microsoft per Excel and VBA: http://support.microsoft.com/kb/257819/en-us. I skimmed through it....didn't really appeal to me lol.