469,327 Members | 1,238 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,327 developers. It's quick & easy.

questions about a View with a Where clause

I'm relatively new to SQL Server & looking for some guidance, if possible. I've been reading lots of different things & am a bit confused about some basics.

I have an Access Project with SQL Server backend. There is a form in the .adp whose record source is a View which contains a WHERE clause.

My questions (and sorry these may be kinda basic):

- I am going to sort the view using a further query.. something like: "SELECT * from vwJobsSummary ORDER BY JobId" -- but I'm not sure where to actually enter that query..

Do I put it into the form's Record Source property (in Access)?
or create a Stored Proc or UDF for it in SQL Server, then call that?
or do I create another View with that query (but a View can't have an Order By clause, can it?! so I get confused again here!)
or do I create a query in Access for this?? (but I thought the idea was to not use Access for tables or queries in this situation.. arrghh! more confusion)

- Next, If I want to change the WHERE clause, do I create a 2nd View to accommodate that, and then update the form's Record Source property via VBA?
or can I dynamically change it somehow?
or should I just scrap the view, and make it a Stored Proc or UDF with parameters, somehow..??

Thanks in advance for any help,
Apr 24 '07 #1
0 1280

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

1 post views Thread by js | last post: by
3 posts views Thread by Evgeny Gopengauz | last post: by
8 posts views Thread by xixi | last post: by
104 posts views Thread by Beowulf | last post: by
30 posts views Thread by James Conrad StJohn Foreman | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
reply views Thread by listenups61195 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.