Does anyone know why the ADP query designer does not support action
queries like the mdb verions does?

mat wrote:
> Does anyone know why the ADP query designer does not support action
> queries like the mdb verions does?

I've almost never done design work from an ADP, I usually do it directly in
SQL Server, so I can't comment on whether or not it's possible to create
action queries graphically from an ADP. I'd be surprised if you couldn't at
all, but as I say, I don't think I've ever even tried.

As for the reason, I would imagine that it's because SQL Server treats
queries and "action queries" as two entirely different things. In SQL
Server, "action queries" are just stored procedures. I'm not 100% certain,
but I believe Access 2000 actually separated the two, but later versions
combined them all under "Queries" to be more like the MDB interface.


Rob

In article <(E-Mail Removed)>,
(E-Mail Removed) says...
> mat wrote:
> > Does anyone know why the ADP query designer does not support action
> > queries like the mdb verions does?
>
> I've almost never done design work from an ADP, I usually do it directly in
> SQL Server, so I can't comment on whether or not it's possible to create
> action queries graphically from an ADP. I'd be surprised if you couldn't at
> all, but as I say, I don't think I've ever even tried.
>
> As for the reason, I would imagine that it's because SQL Server treats
> queries and "action queries" as two entirely different things. In SQL
> Server, "action queries" are just stored procedures. I'm not 100% certain,
> but I believe Access 2000 actually separated the two, but later versions
> combined them all under "Queries" to be more like the MDB interface.
>
>
> Rob
>
I think you're right. But too bad, the regular Access query designer is
a great asset and for complex action queries I really miss it in an adp.
Sprocs can be impossible to represent in a query designer like an mdb
has, but they could have dealt with that by preventing display of sprocs
that were over the line.

Bob;

wrong answer-- ADP _DOES_ support Action queries, they are called
'Stored Procedures'.

I would try being knowledgeable before blindly barging in and telling
someone to do it your way.

-Aaron




On Sep 26, 12:26*am, Robert Morley <rmor...@N0.Freak1n.sparn.magma.ca>
wrote:
> mat wrote:
> > Does anyone know why the ADP query designer does not support action
> > queries like the mdb verions does?
>
> I've almost never done design work from an ADP, I usually do it directly in
> SQL Server, so I can't comment on whether or not it's possible to create
> action queries graphically from an ADP. *I'd be surprised if you couldn't at
> all, but as I say, I don't think I've ever even tried.
>
> As for the reason, I would imagine that it's because SQL Server treats
> queries and "action queries" as two entirely different things. *In SQL
> Server, "action queries" are just stored procedures. *I'm not 100% certain,
> but I believe Access 2000 actually separated the two, but later versions
> combined them all under "Queries" to be more like the MDB interface.
>
> Rob

I don't have a lot of problems using ADP to write Action Queries.

the bottom line is that sprocs can have multiple statements, and
Access queries can only do one thing.

I can take a portion of a SQL Statement (in a sproc) and open it in
design view, and then change it to an update query; without breaking a
swear.
Am I mis-understanding something here?

I just swear it works just like what you are looking for.

Which version are you having trouble with?





On Sep 26, 8:50*am, mat <m...@notarealdotcom.adr> wrote:
> In article <ukae9k6HJHA.1...@TK2MSFTNGP03.phx.gbl>,
> rmor...@N0.Freak1n.sparn.magma.ca says...
>
>
>
> > mat wrote:
> > > Does anyone know why the ADP query designer does not support action
> > > queries like the mdb verions does?
>
> > I've almost never done design work from an ADP, I usually do it directly in
> > SQL Server, so I can't comment on whether or not it's possible to create
> > action queries graphically from an ADP. *I'd be surprised if you couldn't at
> > all, but as I say, I don't think I've ever even tried.
>
> > As for the reason, I would imagine that it's because SQL Server treats
> > queries and "action queries" as two entirely different things. *In SQL
> > Server, "action queries" are just stored procedures. *I'm not 100% certain,
> > but I believe Access 2000 actually separated the two, but later versions
> > combined them all under "Queries" to be more like the MDB interface.
>
> > Rob
>
> I think you're right. But too bad, the regular Access query designer is
> a great asset and for complex action queries I really miss it in an adp.
> Sprocs can be impossible to represent in a query designer like an mdb
> has, but they could have dealt with that by preventing display of sprocs
> that were over the line.- Hide quoted text -
>
> - Show quoted text -

I didn't see your reply till now.

I meant that the ADP graphical query designer does not support action
queries as they are supported by mdb; not that ADP does not support
"action queries". Stored procedures are there for sure and no problem
with them. But I really like the graphical interface that Access
provides for update append delete and make table queries.

I am sure it'd be impossible to provide a completely whole graphical
interface for sprocs. But MS could have provided a graphical designer
interface for UPDATE and other action queries, one would think.

In article <3fc293de-1534-41c6-8988-
(E-Mail Removed)>, (E-Mail Removed)
says...
> I don't have a lot of problems using ADP to write Action Queries.
>
> the bottom line is that sprocs can have multiple statements, and
> Access queries can only do one thing.
>
> I can take a portion of a SQL Statement (in a sproc) and open it in
> design view, and then change it to an update query; without breaking a
> swear.
> Am I mis-understanding something here?
>
> I just swear it works just like what you are looking for.
>
> Which version are you having trouble with?
>
> On Sep 26, 8:50*am, mat <m...@notarealdotcom.adr> wrote:
> > In article <ukae9k6HJHA.1...@TK2MSFTNGP03.phx.gbl>,
> > rmor...@N0.Freak1n.sparn.magma.ca says...
> >
> > > mat wrote:
> > > > Does anyone know why the ADP query designer does not support action
> > > > queries like the mdb verions does?
> >
> > > I've almost never done design work from an ADP, I usually do it directly in
> > > SQL Server, so I can't comment on whether or not it's possible to create
> > > action queries graphically from an ADP. *I'd be surprised if you couldn't at
> > > all, but as I say, I don't think I've ever even tried.
> >
> > > As for the reason, I would imagine that it's because SQL Server treats
> > > queries and "action queries" as two entirely different things. *In SQL
> > > Server, "action queries" are just stored procedures. *I'm not 100% certain,
> > > but I believe Access 2000 actually separated the two, but later versions
> > > combined them all under "Queries" to be more like the MDB interface.
> >
> > > Rob
> >
> > I think you're right. But too bad, the regular Access query designer is
> > a great asset and for complex action queries I really miss it in an adp..
> > Sprocs can be impossible to represent in a query designer like an mdb
> > has, but they could have dealt with that by preventing display of sprocs
> > that were over the line.- Hide quoted text -
> >
> > - Show quoted text -
>
>

Sorry, but the ADP interface _DOES_ support action queries in design
view-- Just like Jet does.

Under the QUERY menu, you can choose 'Query Type'-- just like Jet
does.
a) Under the query tab, hit 'New'.
b) at the 'New Query' menu, select 'design stored procedure'.
c) Under the Query menu, choose 'Make-Table Query'.
d) choose the fields you want.
e) run the query.

It's identical to how it works in Jet, isn't it?

I just find it frustrating when people give false information about
ADP.





On Oct 26, 12:09*pm, mat <m...@notarealdotcom.adr> wrote:
> I didn't see your reply till now.
>
> I meant that the ADP graphical query designer does not support action
> queries as they are supported by mdb; not that ADP does not support
> "action queries". Stored procedures are there for sure and no problem
> with them. But I really like the graphical interface that Access
> provides for update append delete and make table queries.
>
> I am sure it'd be impossible to provide a completely whole graphical
> interface for sprocs. But MS could have provided a graphical designer
> interface for UPDATE and other action queries, one would think.
>
> In article <3fc293de-1534-41c6-8988-
> 456287f77...@u29g2000pro.googlegroups.com>, aaron.ke...@gmail.com
> says...
>
>
>
> > I don't have a lot of problems using ADP to write Action Queries.
>
> > the bottom line is that sprocs can have multiple statements, and
> > Access queries can only do one thing.
>
> > I can take a portion of a SQL Statement (in a sproc) and open it in
> > design view, and then change it to an update query; without breaking a
> > swear.
> > Am I mis-understanding something here?
>
> > I just swear it works just like what you are looking for.
>
> > Which version are you having trouble with?
>
> > On Sep 26, 8:50*am, mat <m...@notarealdotcom.adr> wrote:
> > > In article <ukae9k6HJHA.1...@TK2MSFTNGP03.phx.gbl>,
> > > rmor...@N0.Freak1n.sparn.magma.ca says...
>
> > > > mat wrote:
> > > > > Does anyone know why the ADP query designer does not support action
> > > > > queries like the mdb verions does?
>
> > > > I've almost never done design work from an ADP, I usually do it directly in
> > > > SQL Server, so I can't comment on whether or not it's possible to create
> > > > action queries graphically from an ADP. *I'd be surprised if you couldn't at
> > > > all, but as I say, I don't think I've ever even tried.
>
> > > > As for the reason, I would imagine that it's because SQL Server treats
> > > > queries and "action queries" as two entirely different things. *In SQL
> > > > Server, "action queries" are just stored procedures. *I'm not 100% certain,
> > > > but I believe Access 2000 actually separated the two, but later versions
> > > > combined them all under "Queries" to be more like the MDB interface..
>
> > > > Rob
>
> > > I think you're right. But too bad, the regular Access query designer is
> > > a great asset and for complex action queries I really miss it in an adp.
> > > Sprocs can be impossible to represent in a query designer like an mdb
> > > has, but they could have dealt with that by preventing display of sprocs
> > > that were over the line.- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -

In article <6d7ad67c-3d87-4314-acea-0b2a2170d585
@b38g2000prf.googlegroups.com>, (E-Mail Removed) says...
> Sorry, but the ADP interface _DOES_ support action queries in design
> view-- Just like Jet does.
>
> Under the QUERY menu, you can choose 'Query Type'-- just like Jet
> does.
> a) Under the query tab, hit 'New'.
> b) at the 'New Query' menu, select 'design stored procedure'.
> c) Under the Query menu, choose 'Make-Table Query'.
> d) choose the fields you want.
> e) run the query.
>
> It's identical to how it works in Jet, isn't it?
>
> I just find it frustrating when people give false information about
> ADP.
No kidding - you're right. That's why I posted here, I was hoping
someone one tell me there was a way. I didn't see your reply till now.

It's not quite identical because you have to chose sproc; with a regular
mdb any query starts as a select and you can push it over to a action
query. I think in my tests I chose "design view" for the kind of query.

design view means that you're designing a view.

if you choose Stored Procedure for queries, you shouldn't have to
worry abotu extra keystrokes.



On Nov 26, 9:51*pm, mat <m...@notarealdotcom.adr> wrote:
> In article <6d7ad67c-3d87-4314-acea-0b2a2170d585
> @b38g2000prf.googlegroups.com>, aaron.ke...@gmail.com says...> Sorry, butthe ADP interface _DOES_ support action queries in design
> > view-- Just like Jet does.
>
> > Under the QUERY menu, you can choose 'Query Type'-- just like Jet
> > does.
> > a) Under the query tab, hit 'New'.
> > b) at the 'New Query' menu, select 'design stored procedure'.
> > c) Under the Query menu, choose 'Make-Table Query'.
> > d) choose the fields you want.
> > e) run the query.
>
> > It's identical to how it works in Jet, isn't it?
>
> > I just find it frustrating when people give false information about
> > ADP.
>
> No kidding - you're right. That's why I posted here, I was hoping
> someone one tell me there was a way. I didn't see your reply till now.
>
> It's not quite identical because you have to chose sproc; with a regular
> mdb any query starts as a select and you can push it over to a action
> query. I think in my tests I chose "design view" for the kind of query.