[AccessD] Perhaps I'm just being a dolt...I hope!
Gary Kjos
garykjos at gmail.com
Thu Nov 10 14:46:51 CST 2016
Hi John,
I believe something has happened with your data so that you no longer
have a one to one relationship where you used to have that.
https://support.office.com/en-us/article/Edit-data-in-a-query-6ca3edfc-6d66-4d90-8219-c2b258d5bed7
tells us;
-----------------------------
When can I edit data in a query?
You can always edit the data in a query when the query is based on
either only one table or on two tables that bear a one-to-one
relationship to each other.
Note: Even when you can edit data in a query, some of its fields may
not be available for editing. Such cases are listed in the following
section.
---------------------------and
When can I not edit data in a query?
You can never edit the data in a query when:
The query is a crosstab query.
The query is a SQL-specific query.
The field you are trying to edit is a calculated field. In this case,
you may be able to edit the other fields.
The query is based on three or more tables and there is a
many-to-one-to-many relationship.
Note: Although you cannot edit the query datasheet in this case, you
can edit the data in a form when the RecordsetType property of the
form is set to Dynaset (Inconsistent Updates).
The query contains a GROUP BY clause.
On Thu, Nov 10, 2016 at 2:32 PM, John W. Clark
<John.Clark at niagaracounty.com> wrote:
> I'm praying that this is something simple that I am missing. I'm completely OK with anyone saying, "John, you are being dumb, here is your simple solution..." As illustrated by my general absence, and my rare visits to this list...just can't quit it though...I don't do much with Access these days.
>
>
> But...
>
>
> I have this database downstairs in our treasurers department that has been running smoothly and relatively trouble-free for years. They called me with some weird issues a couple of weeks ago and I ran a "repair and compact" because that is what I do when weird problems arise...again very rare. It did take care of the weirdest of issues, as I figured it might...it was saying a record was already entered that just simply didn't exist. However another issue remains...this is actually not my cause for the help request.
>
>
> My problem is...and this seems to have begun around the same time...SEEMS to have...is that where they were once able to enter a value into their queries, they are no longer able to do this. The one that brought it to light is a date field, which pops up a calendar as it should, but clicking doesn't enter a value, nor can you do it manually. I started looking at other fields and other queries and it is all of them.
>
>
> Also, there are three people that use this database, thus three front-ends among the individual PCs, and I have a copy on mine as well. I checked another, hoping I just needed to copy a new front-end to the offending PC, but it was both (never checked the 3rd...figured it was the same). Then I came up to my computer and tried it with the same results.
>
>
> I thought it was perhaps something to do with filtering which they're using, but no it is all queries. Then I thought perhaps a rights issue with the back-end data, but they are able to enter into forms and tables...I need to double-check the tables statement.
>
>
> No nums-lock, no scroll-lock, I don't know what could cause this...I'm out of ideas. And, I am out of time, we're in the midst of a GroupWise to Exchange migration and I'm swamped as it is. Aahhhh! Please help an unfortunate soul!
>
> Notice: This electronic transmission is intended for the sole use of the individual or entity to which it is addressed and may contain confidential, privileged or otherwise legally protected information. If you are not the intended recipient, or if you believe you are not the intended recipient, you are hereby notified that any use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information, is strictly prohibited. Niagara County is not responsible for the content of any external hyperlink referenced in this email or any email. IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER OR ELECTRONIC COPIES. Thank you for your cooperation.
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
--
Gary Kjos
garykjos at gmail.com
More information about the AccessD
mailing list