UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome Guest ( Log In | Register )

2 Pages V  < 1 2  
Reply to this topicStart new topic
> Dates And Cmd Buttons Not Working On Filter Form    
 
   
projecttoday
post Mar 9 2010, 01:06 AM
Post #21

UtterAccess VIP
Posts: 5,112
From: Dunbar, WV



Not if it's hitting the same query.
Go to the top of the page
 
+
TinkRbelle
post Mar 9 2010, 01:56 AM
Post #22

UtterAccess Addict
Posts: 126
From: San Bernardino CA



QUOTE (projecttoday @ Mar 9 2010, 06:06 AM) *
Not if it's hitting the same query.


I replaced the SQL in the same query. I put the SQL into a new query to test, and when I opened the new query all the records were displayed, not just those on the set date range. What is the expected behavior with this? Perhaps I am not doing the correct steps to test it properly
Go to the top of the page
 
+
TinkRbelle
post Mar 9 2010, 01:56 AM
Post #23

UtterAccess Addict
Posts: 126
From: San Bernardino CA



QUOTE (projecttoday @ Mar 9 2010, 06:06 AM) *
Not if it's hitting the same query.


I replaced the SQL in the same query. I put the SQL into a new query to test, and when I opened the new query all the records were displayed, not just those on the set date range. What is the expected behavior with this? Perhaps I am not doing the correct steps to test it properly
Go to the top of the page
 
+
vtd
post Mar 9 2010, 05:59 AM
Post #24

Retired Moderator
Posts: 19,667



QUOTE (TinkRbelle @ Mar 9 2010, 04:54 PM) *
The other query SQL is for a check registry app, and query is more complicated, but, the Where part regarding the date filtering is what I was mainly referring to.

I have copy/pasted the SQL you have posted here into the related query and when I open the query in datasheet view it does filter the records by the date range you provided, but, when I select any thing from any one of the combo boxes and click the command button on the filter form all records are displayed. Is this expected behavior?

I suggest you stick to one thread rather than concurrent threads that confuse potential respondents. I will stop responding to this thread.
Go to the top of the page
 
+
TinkRbelle
post Mar 10 2010, 02:37 PM
Post #25

UtterAccess Addict
Posts: 126
From: San Bernardino CA



QUOTE (VanThienDinh @ Mar 9 2010, 10:59 AM) *
I suggest you stick to one thread rather than concurrent threads that confuse potential respondents. I will stop responding to this thread.


The topics of my two threads, although involving the same database, are two different issues, involving two different forms, two different command functions using two different queries. That they both involve command buttons should not be a disqualifying factor of posting separate threads for the different problems. I don't understand the confusion between the two being different topics and problems, but, I will consider this thread closed.

Thanks for to all for your time and help.
Go to the top of the page
 
+

2 Pages V  < 1 2
Thank you for your support! Reply to this topicStart new topic

Jump To Forum:
 



RSS Go to Top  ·  Lo-Fi Version Time is now: 18th May 2013 - 07:24 PM