can ASP use access queries?

[mmm, Pie]

I never ever thought about this, but recently I made a query in access so I
can make a customer mailing list based on relational information and it was
so easy to make the query and join tables and assign criterea using access.
And I haven't tried or thought about this cause in my own small asp projects
I've never used a dbase with queries in it, but after seeing how easy it
was, it would save a lot of time from manually writting queries in asp.

So, what I'm asking is if I can use a query from an mdb in asp just like I
can access tables?

And also, is this comparable to a stored procedure in sql?

 

[Ray at]

In Access, the "stored procedures" are called saved queries, and I do
believe you can execute them in the same way you can execute stored
procedures.

http://www.stardeveloper.com/articles/display.html?article=2001050101&page=1
http://www.xefteri.com/articles/apr302002/default.aspx

Ray at work

 

[mmm, Pie]

Thanks for the links, I just started reading the first one.

I'm pretty new at this and I don't actually know anything about Stored
Proceedures, I just heard about them and saved queries in access sound
literally like a stored proceedure

So, just to clarify, a saved query in access is essentially the same thing
as a stored proceedure in an sql dbase?

 

[Ray at]

Well, stored procedures can do more of course, but that's because SQL Server
can so much more. For all intents and purposes, yes, stored procedures are
to SQL Server what saved queries are to Access databases.

Ray at work

 

[Jeff Cochran]

Thanks for the links, I just started reading the first one.

I'm pretty new at this and I don't actually know anything about Stored
Proceedures, I just heard about them and saved queries in access sound
literally like a stored proceedure

So, just to clarify, a saved query in access is essentially the same thing
as a stored proceedure in an sql dbase?

Well, not really.

There are many things in SQL that you simply can't do in Access, so
there are a lot of things a stored procedure can do that a saved query
can't. In addition, a saved query doesn't result in the same
performance gains a stored procedure might, though that's usually a
non-issue if you're using Access anyway since Access won't give the
performance of SQL to start with.

There are also issues with using saved queries when multiple requests
are being handled, mostly due to Access's limited ability to work with
multiple users. Again, by the time you hit these problems you've
likely decided to upgrade to SQL for other reasons anyway.

But for most ASP use, a saved query is really similar to a stored
procedure in use.

Jeff

 

[mmm, Pie]

Thanks guys, that's really cool. I'm excited now )

Great links too, thanks again.