Re: Action queries changing when reopened in design view

From: John Spencer (MVP) (spencer4_at_comcast.net)
Date: 08/30/04 

Date: Mon, 30 Aug 2004 19:01:43 -0400

It would help if you posted the SQL statement vice trying to post a
representation of the view.

Can you copy and post the SQL of your query?

(Possibly unneeded instructions follow)
Open the query
Select View:Sql from the Menu
Select all the text
Copy it
Paste it into the message

Kendra wrote:
>
> Hello,
>
> I am rephrasing/simplifying a question I posted earlier so
> that somebody might know what's going wrong.
>
> I am using two action queries in a form. A delete query
> and an append query. I originally created the queries as
> recommended in Access help, the basic form of each query
> is as follows:
>
> Delete query (please imagine this in design view)
>
> Field: tbl_dataentry adminstatus date
> Table: tbl_dataentry tbl_dataentry tbl_dataentry
> Delete: from where where
> Criteria: [adminstatus]="decline"
> [adminstatus]="decline" etc...
>
> Append query (please imagine this in design view):
> Field: Record_ID Date
> Table: tbl_dataentry tbl_dataentry
> Sort:
> Append to: Record_id Date
> Criteria: [Adminstatus]="accept" [Adminstatus]="accept"
> etc...
>
> However, when I reopen the queries in design view,
> their design has changed from what I originally created.
> Instead of listing the criteria ([Adminstatus]="accept"
> for the append query and [Adminstatus]="deline" for the
> delete query) under each column of my query design view
> (as shown in the query) the very last column of the append
> says "Accept" and "Accept" and "Accept" and the very last
> column of the delete query says "Decline" and "Decline"
> and "Decline" in the criteria section (the field section
> on this last column is the table's name -- tbl_dataentry).
>
> I did not add the last column to my queries' design, nor
> did I delete the criteria sections. I am using these
> queries in a macro that combines the two queries. I
> suspect that running the macro with the queries is what
> altered them, but my queries could just be wrong.
>
> Any suggestions?
> Thank you for your time,
> Kendra

Relevant Pages

  • Re: Is this join valid?
    ... > complex set of tables and queries, but I've boiled down the behavior ... you describe a problem with the Design View that really should not ... affect what happens when running a query from ASP. ... > the SQL view after creating the query in Design View. ...
    (microsoft.public.inetserver.asp.db)
  • seeming quirk with creating new queries from a2000 db /WinXP access/WinXP OS
    ... There is a query property when in the builder ... >from this dbase in Design View. ... >Existing queries that he believes he created as recently ...
    (microsoft.public.access.queries)
  • Re: Stopping query when opening in design view
    ... Within the article is gves a tip about optimizing a query by recompiling it ... by opening it in design view. ... > Microsoft Security Bulletin MS03-026? ... Each of the underlying queries are looking ...
    (microsoft.public.access.queries)
  • Re: save table records from select tempquery
    ... Append query help is right choice for my case. ... my accountant's room) and trying understand best design solution ... sum totals or recall selected aggregated totals as necessary for later ... No, "MakeTable" Queries, just as the name suggests, make an entirely new ...
    (comp.databases.ms-access)
  • Re: Displaying Query Results on a Form
    ... I designed the main table in 'design view'. ... I have built many queries to calculate 'statistical' results. ... "Jeff Boyce" wrote: ... How you query depends on how your data is ...
    (microsoft.public.access.gettingstarted)