Suddenly Locked!!

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Jeremy

    Suddenly Locked!!

    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

    #2
    Re: Suddenly Locked!!-Somebody help!!!

    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.....Sam e 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



    jmsmith@bmi.com (Jeremy) wrote in message news:<c2f60971. 0404191231.5323 c776@posting.go ogle.com>...[color=blue]
    > 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[/color]

    Comment

    • Mike Preston

      #3
      Re: Suddenly Locked!!-Somebody help!!!

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

      mike

      On 20 Apr 2004 13:53:40 -0700, jmsmith@bmi.com (Jeremy) wrote:
      [color=blue]
      >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.....Sam e 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
      >
      >
      >
      >jmsmith@bmi.co m (Jeremy) wrote in message news:<c2f60971. 0404191231.5323 c776@posting.go ogle.com>...[color=green]
      >> 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[/color][/color]

      Comment

      • Jeremy

        #4
        Re: Suddenly Locked!!-Somebody help!!!

        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....ever ything appears to be identical.

        SELECT TBL_TSK_QRT_EVE NT.QRTE_TASKQUA RTER,
        TBL_TSK_QRT_EVE NT.QRTE_COIDLIN K, TBL_TSK_QRT_EVE NT.QRTE_COMPLET E,
        TBL_TSK_QRT_EVE NT.QRTE_USER, TBL_TSK_QRT_EVE NT.QRTE_COMPLET EDATE,
        TBL_TSK_EVENTDR IVEN.EVT_ID, TBL_TSK_EVENTDR IVEN.EVT_EVENTN AME
        FROM TBL_TSK_QRT_EVE NT INNER JOIN TBL_TSK_EVENTDR IVEN ON
        TBL_TSK_QRT_EVE NT.QRTE_TASKLIN K = TBL_TSK_EVENTDR IVEN.EVT_ID
        ORDER BY TBL_TSK_QRT_EVE NT.QRTE_COMPLET EDATE;


        thanks

        js


        mbpatpas.invali d@pacbell.net (Mike Preston) wrote in message news:<4085b66a. 352364563@news. INDIVIDUAL.NET> ...[color=blue]
        > You are likely to get better guidance if you post the SQL.
        >
        > mike
        >
        > On 20 Apr 2004 13:53:40 -0700, jmsmith@bmi.com (Jeremy) wrote:
        >[color=green]
        > >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.....Sam e 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
        > >
        > >
        > >
        > >jmsmith@bmi.co m (Jeremy) wrote in message news:<c2f60971. 0404191231.5323 c776@posting.go ogle.com>...[color=darkred]
        > >> 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[/color][/color][/color]

        Comment

        • Mike Preston

          #5
          Re: Suddenly Locked!!-Somebody help!!!

          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, jmsmith@bmi.com (Jeremy) wrote:
          [color=blue]
          >Glad to offer it...although I don't believe the SQL is the
          >problem...sinc e it's two exactly same statements one that works and
          >one that doesn't....ever ything appears to be identical.
          >
          >SELECT TBL_TSK_QRT_EVE NT.QRTE_TASKQUA RTER,
          >TBL_TSK_QRT_EV ENT.QRTE_COIDLI NK, TBL_TSK_QRT_EVE NT.QRTE_COMPLET E,
          >TBL_TSK_QRT_EV ENT.QRTE_USER, TBL_TSK_QRT_EVE NT.QRTE_COMPLET EDATE,
          >TBL_TSK_EVENTD RIVEN.EVT_ID, TBL_TSK_EVENTDR IVEN.EVT_EVENTN AME
          >FROM TBL_TSK_QRT_EVE NT INNER JOIN TBL_TSK_EVENTDR IVEN ON
          >TBL_TSK_QRT_EV ENT.QRTE_TASKLI NK = TBL_TSK_EVENTDR IVEN.EVT_ID
          >ORDER BY TBL_TSK_QRT_EVE NT.QRTE_COMPLET EDATE;
          >
          >
          >thanks
          >
          >js
          >
          >
          >mbpatpas.inval id@pacbell.net (Mike Preston) wrote in message news:<4085b66a. 352364563@news. INDIVIDUAL.NET> ...[color=green]
          >> You are likely to get better guidance if you post the SQL.
          >>
          >> mike
          >>
          >> On 20 Apr 2004 13:53:40 -0700, jmsmith@bmi.com (Jeremy) wrote:
          >>[color=darkred]
          >> >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.....Sam e 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
          >> >
          >> >
          >> >
          >> >jmsmith@bmi.co m (Jeremy) wrote in message news:<c2f60971. 0404191231.5323 c776@posting.go ogle.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[/color][/color][/color]

          Comment

          • Porkapalooza

            #6
            Re: Suddenly Locked!!-Somebody help!!!

            > > >jmsmith@bmi.co m (Jeremy) wrote in message news:<c2f60971. 0404191231.5323 c776@posting.go ogle.com>...[color=blue][color=green][color=darkred]
            > > >> 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[/color][/color][/color]

            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.

            Comment

            Working...