Re: SQL Problem

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: JMorrell (JMorrell_at_discussions.microsoft.com)
Date: 01/25/05 

Date: Tue, 25 Jan 2005 08:31:02 -0800

Thanks again for the reply.

My Access db is distributed to one user for input and about a dozen users
for view only access. The data sits on our SQL server. All of my queries
sit on each user's pc with the exception of a stored procedure being called
for 2 reports.

As mentioned, I'm a newby with VB and am wanting to eventually make my
application web enabled. I wanted to get my feet wet by creating a windows
app to produce an often-used display screen showing data.

Unless there are other suggestions, I should bone up on stored procedures.

JMorrell

"UAError" wrote:

> "JMorrell" <JMorrell@discussions.microsoft.com> wrote:
>
> >Wow. that certainly says a lot.
> >
> >Did I mention that my Access query includes queries, which include queries?
> >How is that handled with t-sql?
> >
> >tia,
> >JMorrell
> >
> >
>
> The Access "query object" plays the same role as a "view"
> does in a relational database. AFAIK a view may refer to
> another view - though the this may not be desirable for
> other reasons.
>
> Many of these "Access queries" would be better implemented
> as stored procedures in SQL-Server. As stored procedures can
> use other stored procedures, you could minimize your
> duplication of logic and code.
>
> However, while you stated that you are working with
> SQL-Server for the sake of the walkthrough, you didn't
> expressly state that you are going to migrate your data from
> Access to SQL-Server. OleDb can work with an Access database
> file, e.g.:
>
> If you are using Access, you need to use the
> OleDbConnection, OleDbCommand, and OleDbDataAdapter
> object found in the System.Data.OleDb namespace and
> change your connection string to something like the
> following:
>
> "Provider=Microsoft.Jet.OleDb.4.0;
> Data Source=C:\Access\Northwind.mdb"
>
>
> But then you are going to be limited to the functionality
> and syntax of Access.
>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndotnet/html/usingadonet.asp
>
>
> 'Any fool can write code that a computer can understand.
> Good programmers write code that humans can understand.'
> Martin Fowler,
> 'Refactoring: improving the design of existing code', p.15
>

Relevant Pages

  • Re: SQL Problem
    ... >Did I mention that my Access query includes queries, ... does in a relational database. ... as stored procedures in SQL-Server. ... SQL-Server for the sake of the walkthrough, ...
    (microsoft.public.dotnet.general)
  • Re: Access migration to SQL Server
    ... caveat in the first sentence, i.e. remove access all together and you don't ... > about having to convert all your queries to views and stored procedures. ... > using a named query parameter to look up a value from a form control and ...
    (microsoft.public.access.conversion)
  • Re: Access migration to SQL Server
    ... caveat in the first sentence, i.e. remove access all together and you don't ... > about having to convert all your queries to views and stored procedures. ... > using a named query parameter to look up a value from a form control and ...
    (microsoft.public.sqlserver.server)
  • Re: Off Topic - Access to Postgres
    ... >>However, I find that using views, stored procedures and pass through queries ... >procedures and pass-through queries. ... >The reason pass-through queries are a problem for Access (and stored ... - To the extent that your application relies on server-side objects, ...
    (comp.databases.ms-access)
  • Re: Off Topic - Access to Postgres
    ... If sprocs and pass through queries are not the solution then ... >However, I find that using views, stored procedures and pass through queries ... The reason pass-through queries are a problem for Access (and stored ... may have to create a saved pass-through query, ...
    (comp.databases.ms-access)