Re: Recommended? Access + DAO + SQLServer 2000 + ODBC



Using Now() as a criteria, if you have a fairly simple query,
Now() should be evaluated by Jet/VBA, and the value sent to
SQL Server, which would then try to match that value (using
an index if available), and if you were lucky, return a
matching record.

If you were unlucky, you would fail, because time values
are stored differently in SQL Server.

Because time values are stored differently, you can't be
sure that time values will match exactly.

More complex queries (particularly those with Left or Right
Joins) may download enough of the records to do the Joins
locally, and criteria may be evaluated locally, but you still
will have trouble with Now(), because when you get a time
value back, it may not be exactly the same as a time value
you sent.

(david)


"Savvoulidis Iordanis" <iordanis_sav@xxxxxxxxxxx> wrote in message
news:%237z$qNmIGHA.3700@xxxxxxxxxxxxxxxxxxxxxxx
> Thank you all. Probably I'll try the terminal server solution at first
> (which has no app changes)
>
> But anyway, if some of my queries, use the Now() function in the criteria,
> how can this be used in Access MDE and ODBC connection to SQL Server? Are
> there any changes that I should make to my queries or code, in the SQL
> Server scenario?
>
>


.



Relevant Pages

  • RE: time criteria in query
    ... "Harry F." ... I don't have access to the actual SQL server ... in which case you'd surround your date criteria with single-quotes ... Which date/time type are you using in Sql Server? ...
    (microsoft.public.access.queries)
  • Re: time criteria in query
    ... Or...start a query with just the date field ... "Harry F."wrote: ... criteria, it does actually return the time value properly. ... SQL Server with ODBC, Access should use DAO and therefore require the ...
    (microsoft.public.access.queries)
  • RE: data wont be displayed in the form
    ... criteria specified in the SQL server view, ... > form because it doesn't satisfy the criteria in the underlying record source" ... > There are no filters, no server filters, no form filters, no where clauses. ...
    (microsoft.public.access.modulesdaovba)
  • Re: Migration from mdb to MS SQL Server
    ... Hey Rick --- ... I have seen filters and criteria get it ... I always use integer fields for this now on the SQL Server. ... Rick Brandt, Microsoft Access MVP ...
    (microsoft.public.access.formscoding)
  • Re: Access project (with SQL server)
    ... Does the data you're trying to insert meet that criteria? ... > To avoid this problem set the RecordSource property of the Subform to a ... > Upgrade to a newer version of Microsoft SQL Server. ... > More information about this error message online. ...
    (microsoft.public.access.modulesdaovba)