1. Forum
  2. USENET
  3. comp.databases.ms-sqlserv

  • Replacing a corrupted Query

    From Peter Jason@pj@jostle.com to comp.databases.ms-access on Wed Jun 30 17:05:49 2021
    From Newsgroup: comp.databases.ms-sqlserv

    I suspect one of my queries is corrupted. Older ones from past
    backups work well, so I ask if I can replace the newer corrupted ones
    with the working older ones? How does one do this; is it just copy &
    paste? These are update, select, delete & make-table queries.
    P
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Cindy Krist@cindy@smbpartners.com to comp.databases.ms-access on Wed Jun 30 04:52:53 2021
    From Newsgroup: comp.databases.ms-sqlserv

    Peter,
    Go to a backup, display the query in SQL view, copy it.
    Go to the production database, create a new query, view it in SQL, paste it.
    If you go into Design view, you can move the tables around to make it more readable.
    Regards,
    Cindy
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Peter Jason@pj@jostle.com to comp.databases.ms-access on Thu Jul 1 07:24:06 2021
    From Newsgroup: comp.databases.ms-sqlserv

    On Wed, 30 Jun 2021 04:52:53 -0700 (PDT), Cindy Krist
    <cindy@smbpartners.com> wrote:

    Peter,
    Go to a backup, display the query in SQL view, copy it.
    Go to the production database, create a new query, view it in SQL, paste it. >If you go into Design view, you can move the tables around to make it more readable.
    Regards,
    Cindy

    Thank you Cindy, I'll report back with the results if any. There are
    many many queries to check.
    Peter
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Auntie Jack@raycorbin1@gmail.com to comp.databases.ms-access on Wed Jun 30 23:00:15 2021
    From Newsgroup: comp.databases.ms-sqlserv

    Alternatively, import the queries from the old database. If you have 2016 or 365, that would be: External Data \ New Data Source \ From Database \ Access, If you have quite a few queries to import, that will make it quicker. Also, if one or more is corrupted, then you will probably find that Access interrupts the import when it encounters the corrupt one. That can make it easier to spot where the error is.
    Jack
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Peter Jason@pj@jostle.com to comp.databases.ms-access on Fri Jul 23 17:24:27 2021
    From Newsgroup: comp.databases.ms-sqlserv

    On Wed, 30 Jun 2021 23:00:15 -0700 (PDT), Auntie Jack
    <raycorbin1@gmail.com> wrote:

    Alternatively, import the queries from the old database. If you have 2016 or 365, that would be: External Data \ New Data Source \ From Database \ Access, If you have quite a few queries to import, that will make it quicker. Also, if one or more is corrupted, then you will probably find that Access interrupts the import when it encounters the corrupt one. That can make it easier to spot where the error is.
    Jack

    Thanks to all.

    The problem was not a corrupted query. It was when I coasted products
    in my 4-level BOM query I had neglected to filter out all levels
    except 0. This fixed the problem of cost duplicates.

    Thanks again.

    --- Synchronet 3.21d-Linux NewsLink 1.2