Findfirst Date format

[Jane]

I posted a question yesterday, asking for help with a date
format in DAO criteria. I changed the format and the date
criteria worked fine. I thought I would use the example as
the basis for other criteria? No such luck! the folllowing
findfirst line works fine if any of the criteria is
applied idependently, but fails if coupled. Any further
help would be appreciated also any pointers to on line
documents dealing with this issue please.

On this occaision the string searched for first is held in
a string variable.


rstCalen.FindFirst "[eventname] = """ & DDive & """"
And "[start] = " & Format$(Tdate, "\#mm\/dd\/yyyy\#")

Thanks Jane

 

[Douglas J. Steele]

And has to be in the string:

rstCalen.FindFirst "[eventname] = """ & DDive & """ And [start] = " &
Format$(Tdate, "\#mm\/dd\/yyyy\#")

 

[Guest]

Thanks again, hopefully I will have a better grasp now.
But I would still like to read any articles available, if
they are out there.
until the next time
Jane

-----Original Message-----
And has to be in the string:

rstCalen.FindFirst "[eventname] = """ & DDive & """ And [start] = " &
Format$(Tdate, "\#mm\/dd\/yyyy\#")


--
Doug Steele, Microsoft Access MVP

(No private e-mails, please)

I posted a question yesterday, asking for help with a date
format in DAO criteria. I changed the format and the date
criteria worked fine. I thought I would use the example as
the basis for other criteria? No such luck! the folllowing
findfirst line works fine if any of the criteria is
applied idependently, but fails if coupled. Any further
help would be appreciated also any pointers to on line
documents dealing with this issue please.

On this occaision the string searched for first is held in
a string variable.


rstCalen.FindFirst "[eventname] = """ & DDive & """"
And "[start] = " & Format$(Tdate, "\#mm\/dd\/yyyy\#")

Thanks Jane

.

 

[Tim Ferguson]

But I would still like to read any articles available, if
they are out there.
until the next time

Try the help files for the WHERE clause. There are also pages on using
literal values in SQL commands.

HTH


Tim F