Jim
I make my views directly in SQL Server Management Studio. I write the SQL, but you can also use the wizard which is very similar to Access's Query Designer.
T-SQL is not exactly like Access JET SQL as you are probably learning. IIF blocks must be written as CASE blocks. And wild cards are % and _ instead of * and ?
But you might be able to just copy your Access query SQL into a new query in SQLS. If it runs you're all set. Then put this line at the top:
CREATE VIEW yourQueryNameGoesHere AS
and run it. That will create the view. Refresh the object explorer to get the new view to show up. Once you're done you can link to the view just like a table.
Bill
--- In MS_Access_Professionals@yahoogroups.com, Jim Wagner <luvmymelody@...> wrote:
>
> Bill,
>
> Most of the google and bing has indicated that a view in Access is unstable or not able to do. How do I create a view that works?
>
> Thank You
> Â
> Jim Wagner
> ________________________________
>
>
>
> ________________________________
> From: Bill Mosca <wrmosca@...>
> To: MS_Access_Professionals@yahoogroups.com
> Sent: Wednesday, July 17, 2013 9:13 AM
> Subject: Re: [MS_AccessPros] Query Performance question
>
>
>
> Â
> Jim
>
> A view is the best way to go. In most cases it's much faster than an Access query.
>
> Bill
>
> --- In MS_Access_Professionals@yahoogroups.com, Jim Wagner <luvmymelody@> wrote:
> >
> > Thank You everyone for your suggestions.ÂÂ
> > I ask the question because I am learning SQL and we are on views. We seem to use these same several tables in queries and thought about creating some type of view or table to use as the basis for the other queries and reports. I guess performance was kind of the wrong way to ask the question.
> > ÂÂ
> > Jim Wagner
> > ________________________________
> >
> >
> >
> > ________________________________
> > From: John Viescas <JohnV@>
> > To: MS_Access_Professionals@yahoogroups.com
> > Sent: Tuesday, July 16, 2013 2:37 PM
> > Subject: RE: [MS_AccessPros] Query Performance question
> >
> >
> >
> > ÂÂ
> > Jim-
> >
> > A Make Table is always going to be a bit slower to open the report once.
> > But if you need to open the report multiple times on the same data, then the
> > Make Table will ultimately be faster. The secret to making queries run
> > faster is to link the tables on keys that have been defined in referential
> > integrity rules and to place indexes on all fields that you filter.
> >
> > John Viescas, Author
> > Microsoft Access 2010 Inside Out
> > Microsoft Access 2007 Inside Out
> > Microsoft Access 2003 Inside Out
> > Building Microsoft Access Applications
> > SQL Queries for Mere Mortals
> > http://www.viescas.com/
> > (Paris, France)
> >
> > -----Original Message-----
> > From: MS_Access_Professionals@yahoogroups.com
> > [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of luvmymelody
> > Sent: Tuesday, July 16, 2013 6:06 PM
> > To: MS_Access_Professionals@yahoogroups.com
> > Subject: [MS_AccessPros] Query Performance question
> >
> > Hello all,
> >
> > I have a question about query performance.
> >
> > What would be faster to use for a report?
> > I have several reports that are based on the same multi table query, but
> > with different criteria across the grid. It would be almost like a View in
> > SQL.
> >
> > Thank You
> >
> > Jim Wagner
> >
> > A query with 3 tables in the design view with the criteria in the grid
> >
> > OR
> >
> > A Make table query that has all the tables and criteria being used for the
> > source of the report
> >
> > ------------------------------------
> >
> > Yahoo! Groups Links
> >
> >
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
> [Non-text portions of this message have been removed]
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (9) |
Tidak ada komentar:
Posting Komentar