I have a stored procedure that uses the code I posted above to return
any client that matches on at least 5 of the 7 fields. So it seems like
it can be done in SQL Server. I'm just wondering if there is a similar
why to do it in Access, or am I going to have to do what you describe
and have 21 different queries to get all the possible matches. I hope I
don't have to do that!
Re: Access And SQL Server with ODBC ...Savvoulidis Iordanis wrote: ... If I move the data only, to a SQL Server, which Access links to it, ... plain old local queries against ODBC ... Sometimes the passthrough or stored procedure will ... (microsoft.public.access.formscoding)
Re: SQLServer Stored Procedure Error Control over DataReader ... > I've made a stored procedure that applies some actions, ... The errors are just messages to the client,... SqlClient is unfortunately hard-coded to throw a SqlException and ignore all ... And Sql Server doesn't support ... (microsoft.public.dotnet.framework)
Re: SQL Server - Filter ... Happy to use a stored procedure but prefer to use a View that can be linked ... >> the sql server tables from access you are pretty much defeating the idea ... > many fewer bugs if they'd just used Access queries for the most part. ... > to query data from the back-end. ... (comp.databases.ms-access)
Re: iis/asp + sql2000 a bit slow ... >> encapsulate your queries into a stored procedure. ... >> much processing in the client.... The difference is that with a stored procedure you send one command to the ... I'm sure if you use SQL Profiler to trace the database server activity,... (microsoft.public.inetserver.asp.db)
Random long running queries ... In fact two days ago we changed one of the queries to a stored ... However the stored procedure (or query keep running till the bitter end). ... Any ideas as to what can cause SQL Server to suddenly act like it is frozen ... (microsoft.public.sqlserver.odbc)
