By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,027 Members | 1,261 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,027 IT Pros & Developers. It's quick & easy.

Time key is not updateable!! HELP!!

P: n/a
I have a sql database connected with access, but when I try to run
macros which basically just transfer information from tables for
approval an error comes up with "time key is not updateable". I have
found a quick fix in which I can delete the time key from the table
and everything will run fine, but when end users try to change
records
it will not allow them. It comes up with an error that they cannot
save changes and must copy to the clipboard. Which then makes me have
to put the time key back and only then can they make changes. If you
have any suggestions please help!! If you need some more
clarification
please let me know.

Sep 4 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On Tue, 04 Sep 2007 07:33:51 -0700, ki********@hotmail.com wrote:
>I have a sql database connected with access, but when I try to run
macros which basically just transfer information from tables for
approval an error comes up with "time key is not updateable". I have
found a quick fix in which I can delete the time key from the table
and everything will run fine, but when end users try to change
records
it will not allow them. It comes up with an error that they cannot
save changes and must copy to the clipboard. Which then makes me have
to put the time key back and only then can they make changes. If you
have any suggestions please help!! If you need some more
clarification
please let me know.
I rather suspect Access is simply giving you the wrong error message,
and the error really has nothing at all to deal with the problem, it
is just one that fits the scenario of one where an update via the form
cannot be accomplished.

There could be quite a few explanations of this problem, but without
actually seeing your database, there's no easy way to tell you what
the exact problem is.

When dealing with access front-ends to SQL Server based back-ends,
whenever you make a "low-level" change to the structure (or working)
of a table (or view), you *MUST* have the users drop and re-create any
links they have to that table or view. This also means any tables (in
access) that are (in reality) views on the server. A table or view
may *appear* to work, but in use there may be some quite disastrous
results.

You will also have to do this when a field that used to allow nulls is
changed to not allow nulls. There are a number of other conditional
changes that can cause this error, the "allowing nulls" to "not
allowing nulls" is just the one I've seen most often. Changing a
field type such as changing a field from Char (or VarChar) to DateTime
is another.

Sep 9 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.