Suddenly Locked!!

[Jeremy]

I have an access db in which a for based on a simple query is updated
by the user. It has been being used for a year that way...now it
suddenly does not allow an update. The symptom has specific features
in that, The data cannot be updated in the query, it only beeps,
however the typical "non updateable query" message does not show
up...so it is a different problem. I changed some other code...but
should hjave been unrealted and this query in it's basic for should
work fine. It is simple a data table with one reference table linked
to it...and it has been easily updatable for a good while. I can find
no properties changed...is there any kind of status that comes to mind
I could have changed??

Please only answer the question above and try not to suggest things
outside of the above perameters as it just wastes poting time. The
query worked before and now does not.

Thanks for your thoughts.

Jeremy Smith

[Jeremy]

And More.......

Ok...I Isolated this problem....I pulled the two tables into a new dB
and the query. I also pulled the two tables from a working production
version and the query in that version.....Same results....the first
one does not work the socnd one allows me to manually update fine.....

Every Property on the tables and query appear to be the same...but
something is locking the query from be able to update...still no
"non-updatable" message.

Thanks

Jeremy SMith

jm*****@bmi.com (Jeremy) wrote in message news:<c2**************************@posting.google. com>...

I have an access db in which a for based on a simple query is updated
by the user. It has been being used for a year that way...now it
suddenly does not allow an update. The symptom has specific features
in that, The data cannot be updated in the query, it only beeps,
however the typical "non updateable query" message does not show
up...so it is a different problem. I changed some other code...but
should hjave been unrealted and this query in it's basic for should
work fine. It is simple a data table with one reference table linked
to it...and it has been easily updatable for a good while. I can find
no properties changed...is there any kind of status that comes to mind
I could have changed??

Please only answer the question above and try not to suggest things
outside of the above perameters as it just wastes poting time. The
query worked before and now does not.

Thanks for your thoughts.

Jeremy Smith

[Mike Preston]

You are likely to get better guidance if you post the SQL.

mike

On 20 Apr 2004 13:53:40 -0700, jm*****@bmi.com (Jeremy) wrote:

And More.......

Ok...I Isolated this problem....I pulled the two tables into a new dB
and the query. I also pulled the two tables from a working production
version and the query in that version.....Same results....the first
one does not work the socnd one allows me to manually update fine.....

Every Property on the tables and query appear to be the same...but
something is locking the query from be able to update...still no
"non-updatable" message.

Thanks

Jeremy SMith

jm*****@bmi.com (Jeremy) wrote in message news:<c2**************************@posting.google. com>...

I have an access db in which a for based on a simple query is updated
by the user. It has been being used for a year that way...now it
suddenly does not allow an update. The symptom has specific features
in that, The data cannot be updated in the query, it only beeps,
however the typical "non updateable query" message does not show
up...so it is a different problem. I changed some other code...but
should hjave been unrealted and this query in it's basic for should
work fine. It is simple a data table with one reference table linked
to it...and it has been easily updatable for a good while. I can find
no properties changed...is there any kind of status that comes to mind
I could have changed??

Please only answer the question above and try not to suggest things
outside of the above perameters as it just wastes poting time. The
query worked before and now does not.

Thanks for your thoughts.

Jeremy Smith

[Jeremy]

Glad to offer it...although I don't believe the SQL is the
problem...since it's two exactly same statements one that works and
one that doesn't....everything appears to be identical.

SELECT TBL_TSK_QRT_EVENT.QRTE_TASKQUARTER,
TBL_TSK_QRT_EVENT.QRTE_COIDLINK, TBL_TSK_QRT_EVENT.QRTE_COMPLETE,
TBL_TSK_QRT_EVENT.QRTE_USER, TBL_TSK_QRT_EVENT.QRTE_COMPLETEDATE,
TBL_TSK_EVENTDRIVEN.EVT_ID, TBL_TSK_EVENTDRIVEN.EVT_EVENTNAME
FROM TBL_TSK_QRT_EVENT INNER JOIN TBL_TSK_EVENTDRIVEN ON
TBL_TSK_QRT_EVENT.QRTE_TASKLINK = TBL_TSK_EVENTDRIVEN.EVT_ID
ORDER BY TBL_TSK_QRT_EVENT.QRTE_COMPLETEDATE;
thanks

js
mb**************@pacbell.net (Mike Preston) wrote in message news:<40****************@news.INDIVIDUAL.NET>...

You are likely to get better guidance if you post the SQL.

mike

On 20 Apr 2004 13:53:40 -0700, jm*****@bmi.com (Jeremy) wrote:

And More.......

Ok...I Isolated this problem....I pulled the two tables into a new dB
and the query. I also pulled the two tables from a working production
version and the query in that version.....Same results....the first
one does not work the socnd one allows me to manually update fine.....

Every Property on the tables and query appear to be the same...but
something is locking the query from be able to update...still no
"non-updatable" message.

Thanks

Jeremy SMith

jm*****@bmi.com (Jeremy) wrote in message news:<c2**************************@posting.google. com>...

I have an access db in which a for based on a simple query is updated
by the user. It has been being used for a year that way...now it
suddenly does not allow an update. The symptom has specific features
in that, The data cannot be updated in the query, it only beeps,
however the typical "non updateable query" message does not show
up...so it is a different problem. I changed some other code...but
should hjave been unrealted and this query in it's basic for should
work fine. It is simple a data table with one reference table linked
to it...and it has been easily updatable for a good while. I can find
no properties changed...is there any kind of status that comes to mind
I could have changed??

Please only answer the question above and try not to suggest things
outside of the above perameters as it just wastes poting time. The
query worked before and now does not.

Thanks for your thoughts.

Jeremy Smith

[Mike Preston]

It sounds like there is a dependency that is not working.

That would certainly explain why a brand new mdb with merely these two
tables and this query would also stop working.

In the production app are any of the fields being selected themselves
referenced in the relationships documentation by yet a third table?

Just grasping here.

mike
On 21 Apr 2004 07:03:55 -0700, jm*****@bmi.com (Jeremy) wrote:

Glad to offer it...although I don't believe the SQL is the
problem...since it's two exactly same statements one that works and
one that doesn't....everything appears to be identical.

SELECT TBL_TSK_QRT_EVENT.QRTE_TASKQUARTER,
TBL_TSK_QRT_EVENT.QRTE_COIDLINK, TBL_TSK_QRT_EVENT.QRTE_COMPLETE,
TBL_TSK_QRT_EVENT.QRTE_USER, TBL_TSK_QRT_EVENT.QRTE_COMPLETEDATE,
TBL_TSK_EVENTDRIVEN.EVT_ID, TBL_TSK_EVENTDRIVEN.EVT_EVENTNAME
FROM TBL_TSK_QRT_EVENT INNER JOIN TBL_TSK_EVENTDRIVEN ON
TBL_TSK_QRT_EVENT.QRTE_TASKLINK = TBL_TSK_EVENTDRIVEN.EVT_ID
ORDER BY TBL_TSK_QRT_EVENT.QRTE_COMPLETEDATE;
thanks

js
mb**************@pacbell.net (Mike Preston) wrote in message news:<40****************@news.INDIVIDUAL.NET>...

You are likely to get better guidance if you post the SQL.

mike

On 20 Apr 2004 13:53:40 -0700, jm*****@bmi.com (Jeremy) wrote:

>And More.......
>
>Ok...I Isolated this problem....I pulled the two tables into a new dB
>and the query. I also pulled the two tables from a working production
>version and the query in that version.....Same results....the first
>one does not work the socnd one allows me to manually update fine.....
>
>Every Property on the tables and query appear to be the same...but
>something is locking the query from be able to update...still no
>"non-updatable" message.
>
>Thanks
>
>Jeremy SMith
>
>
>
>jm*****@bmi.com (Jeremy) wrote in message news:<c2**************************@posting.google. com>...
>> I have an access db in which a for based on a simple query is updated
>> by the user. It has been being used for a year that way...now it
>> suddenly does not allow an update. The symptom has specific features
>> in that, The data cannot be updated in the query, it only beeps,
>> however the typical "non updateable query" message does not show
>> up...so it is a different problem. I changed some other code...but
>> should hjave been unrealted and this query in it's basic for should
>> work fine. It is simple a data table with one reference table linked
>> to it...and it has been easily updatable for a good while. I can find
>> no properties changed...is there any kind of status that comes to mind
>> I could have changed??
>>
>> Please only answer the question above and try not to suggest things
>> outside of the above perameters as it just wastes poting time. The
>> query worked before and now does not.
>>
>> Thanks for your thoughts.
>>
>> Jeremy Smith

[Porkapalooza]

> > >jm*****@bmi.com (Jeremy) wrote in message news:<c2**************************@posting.google. com>...

> I have an access db in which a for based on a simple query is updated
> by the user. It has been being used for a year that way...now it
> suddenly does not allow an update. The symptom has specific features
> in that, The data cannot be updated in the query, it only beeps,
> however the typical "non updateable query" message does not show
> up...so it is a different problem. I changed some other code...but
> should hjave been unrealted and this query in it's basic for should
> work fine. It is simple a data table with one reference table linked
> to it...and it has been easily updatable for a good while. I can find
> no properties changed...is there any kind of status that comes to mind
> I could have changed??
>
> Please only answer the question above and try not to suggest things
> outside of the above perameters as it just wastes poting time. The
> query worked before and now does not.
>
> Thanks for your thoughts.
>
> Jeremy Smith

I just had a similar problem a few weeks ago - I found that I had lost
one of my primary keys in a table - check that (and your relationship
table) to see if it helps.