I'm using VBA in Access. I have a table with the date format set to "mmm-yy". In VBA I also have the date format set to "mmm-yy". In doing a seek on the table, I'm getting a hit on "Jan-00" even though the argument I'm using is "Jan-01". It acts like the system is reading Jan-01 as January 1st, even though the format is mmm-yy. So, rather than adding records for 2001, I'm editing the records for 2000 - not what I had in mind. Any suggestions?<br><br>Thanks - Ham
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Date compares
- Thread starter Ham
- Start date
listener22
Programmer
I'm a little rusty on this access date problem, but had to deal with<br>it a couple of years ago when using vb as an access front-end. If I<br>remember right, the choice you make for the access table format<br>has no affect on queries, matching, etc. It is only for display purposes.<br>However, you can test this by running a query or two directly in<br>access.<br> I also have a vague recollection that the date format chosen in windows<br>has an affect on how access matches dates. Again, that can be tested<br>with an access query or two. My guess is that you'll have to use the<br>standard mm/dd/yy format in an access query and in your vba, if that<br>is your default windows format. Just a guess, though.<br><br> <p>Jim Carlson<br><a href=mailto:nx56@inetarena.com>nx56@inetarena.com</a><br><a href= > </a><br>oracle, vb, some javascript
- Status
