Query Types in Query Designer

I am just beginning to use SQL Server(MSDE), Access 2003 adp projects in a
web application I am developing. In using the query designer I am given the
option of developing a View or a Function in addition to a Stored Procedure.
I know about Stored Procedures but I have no information on when and how to
use Views or Functions. Can someone give me some insight on what
circumstances would cause you to select one query type over another and/or
point me to some documentation that will?
Through trial and error I have found that you can’t have a computed column
in a Function but you can in a View and you can sort in a Function but you
can’t in a View. I am investing quite a bit of effort into this project and
I don’t want to get down the road too far and find out that I have made some
basic mistake that will require substantial rework.
Any help you can give will be greatly appreciated.
Ray Cannon
EIS, Inc.
Access is generally not the best choice for web applications. It is
also not the best choice of development tools for a SQL Server
database. It is a better idea to purchase the Developer edition of SQL
Server ($49) that has the client tools and use it to create your SQL
Server objects. Use MSDE only when it comes time to deploy your
application. The license agreement for the Developer edition prohibits
its use in a production environment, but it has everything you need to
create, test and secure SQL Server databases. SQL Books Online is a
good source of information on creating SQL Server objects, as are
third-party books. You can download the latest version at
http://www.microsoft.com/sql/techinf...2000/books.asp
-- Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446
On Wed, 4 Aug 2004 12:15:04 -0700, "RayC"
<RayC@.discussions.microsoft.com> wrote:

> I am just beginning to use SQL Server(MSDE), Access 2003 adp projects in a
>web application I am developing. In using the query designer I am given the
>option of developing a View or a Function in addition to a Stored Procedure.
>I know about Stored Procedures but I have no information on when and how to
>use Views or Functions. Can someone give me some insight on what
>circumstances would cause you to select one query type over another and/or
>point me to some documentation that will?
>Through trial and error I have found that you cant have a computed column
>in a Function but you can in a View and you can sort in a Function but you
>cant in a View. I am investing quite a bit of effort into this project and
>I dont want to get down the road too far and find out that I have made some
>basic mistake that will require substantial rework.
>Any help you can give will be greatly appreciated.

Query timeout problems

Front End: Access 2000 Project (.adp)
Back End: SQL Server 2000

I have an application that keeps timing out. I have opened the
DataLink properties in the front end (File, Connection, Advanced tab)
and set the timeout to 999. But the connection still occasionally
times out.

Any ideas? Some of the SQL is pretty horrible (multiple sub-queries
etc.)

TIA

Edward
--
The reading group's reading group:
http://www.bookgroup.org.uk"Edward" <teddysnips@.hotmail.com> wrote in message
news:25080b60.0501310730.3f8e6ed9@.posting.google.c om...
> Front End: Access 2000 Project (.adp)
> Back End: SQL Server 2000
> I have an application that keeps timing out. I have opened the
> DataLink properties in the front end (File, Connection, Advanced tab)
> and set the timeout to 999. But the connection still occasionally
> times out.
> Any ideas? Some of the SQL is pretty horrible (multiple sub-queries
> etc.)
> TIA
> Edward
> --
> The reading group's reading group:
> http://www.bookgroup.org.uk

The timeout you changed is the connection timeout, so it won't affect
timeouts caused by long-running queries. Depending on what connection
library you're using (ODBC, ADO), you should be able to change the general
timeout value, but I have no idea how - perhaps an Access group might give
more help.

In ay event, if the timeouts occur during different queries, or the same
queries with different parameters, you'll probably have to try to identify
the problem queries more exactly - Profiler would be a good place to start.

Simon