Error 3027: cannot update: database or object is read only

[PaulB]

Hi there,

Allthough I searched for previous posts, I was unable to solve my problem.

I try to link my front-mdb with an Excel file using the next line
DoCmd.TransferSpreadsheet acLink, 8, "TblParameters",
"C:\Parameters.xls", True, ""

This works perfect for Access 2000, while for Access 2002 and Access
2003 I get error message 3027: cannot update: database or object is read
only.
The file is linked (fields can be read), but I'm unable to update any
fields.

And of course, I checked that this problem was not related to read-only
attribute, administrator rigths, etc.

Who has any suggestions to solve this? Any help is appreciated greatly!

Paul

 

[Douglas J Steele]

Unfortunately, there has been a legal problem that's forced Microsoft to
turn off the ability to update Excel from Access.

http://support.microsoft.com/?id=904953

In addition to the work-arounds mentioned, you can also use Automation.

 

[PaulB]

Douglas: Thank you very much for this. This makes my problem clear!
Can you tell me somewhat more about 'automation' part? What are the
principles, possibilities and limitations? (I know these questions are
very wide, and difficult to answer fully). But 'automation' is
completely new to me.
So, this was the polite part.

And now the angry part: why the f**ck is Microsoft changing this? If you
have a legal version of the Office package, why can't you use it in an
integrated manner??? I developped an application which I sold to many
users. Some of them use A2000, some of them A2002/A2003. So I have to
redesign my application :-((
Microsoft: thank you very much!!

 

[Douglas J Steele]

I'm sure it'll be little consolation, but it wasn't Microsoft's idea!
http://news.com.com/Patent+ruling+costs+Microsoft+8.9+million/2100-1007_3-5735432.html

I'm having problems finding a comprehensive reference to automating Excel
from Access.

http://support.microsoft.com/?id=142476 will give you a brief introduction,
and http://support.microsoft.com/?id=247412 is applicable as well (even
though it doesn't specifically mention Access)

While it's a little dated, http://support.microsoft.com/?id=260410 should
help as well.

 

[PaulB]

Hi Douglas,

One again, thank you very much! Of course, I did not have the time yet
to have a detailed look at it, but sure I will.

Seems like Microsoft was again using other people's
inventions/creations... When do they learn from that?

Paul