P
Pete B
Very frustrated. I've seen this before with Access and fixed it but cant'
tell you how!! The problem comes and goes. It has just re-surfaced after
being gone for over two years.
The problem is using "seek" in VBA against a table that contains dates.
1) The index is first set on the date/time field in which I will seek.
2) The seek is then performed using the "=" seek parameter.
3) It doesn't find it.....
Is this a known problem? Is there a fix?
Notes:
1) The searched date/time DOES match an existing date/time in the table.
2) Using ">=" as the seek operator finds the record!! But using this method
doesn't solve my problem in all cases.
3) When I use ">=" in the debug mode, I've added debug code that tests the
value in the found record against the sought value and VBA tells me the two
values are NOT equal (although the really are!!)
tell you how!! The problem comes and goes. It has just re-surfaced after
being gone for over two years.
The problem is using "seek" in VBA against a table that contains dates.
1) The index is first set on the date/time field in which I will seek.
2) The seek is then performed using the "=" seek parameter.
3) It doesn't find it.....
Is this a known problem? Is there a fix?
Notes:
1) The searched date/time DOES match an existing date/time in the table.
2) Using ">=" as the seek operator finds the record!! But using this method
doesn't solve my problem in all cases.
3) When I use ">=" in the debug mode, I've added debug code that tests the
value in the found record against the sought value and VBA tells me the two
values are NOT equal (although the really are!!)