Access sql query based on user provided date only returns dates with times = 0:00:00










1















Haven't found any closely related questions, so here goes.



This is a simple version of my query:



SELECT sampleID, beginDateTime
FROM sample
WHERE DateValue(beginDateTime) = [Enter sample date: ];


This returns no records but should return 3 based on the date I entered.



However, this version returns what I expect, all the records that match the supplied date and their respective times.



SELECT sampleID, beginDateTime
FROM sample
WHERE DateValue(beginDateTime) = #2015-5-18#;


How can I enable a user prompt that is properly formatted in Access SQL that will return the appropriate records? Note: I don't know VBA.



Also tried adding PARAMETER = beginDateTime DateTime; This seems to return all records and assigns them all the date that the user was prompted for.



Tried using DateValue in the parameter list:



SELECT sampleID, DateValue(beginDateTime)
FROM sample
WHERE beginDateTime = [Enter sample date: ];


This only returns dates = 0:00:00



I'd like my query to prompt the user for a date (without a time) and return all records with that date along with their respective times.



I would appreciate your help very much. Thanks in advance.










share|improve this question




























    1















    Haven't found any closely related questions, so here goes.



    This is a simple version of my query:



    SELECT sampleID, beginDateTime
    FROM sample
    WHERE DateValue(beginDateTime) = [Enter sample date: ];


    This returns no records but should return 3 based on the date I entered.



    However, this version returns what I expect, all the records that match the supplied date and their respective times.



    SELECT sampleID, beginDateTime
    FROM sample
    WHERE DateValue(beginDateTime) = #2015-5-18#;


    How can I enable a user prompt that is properly formatted in Access SQL that will return the appropriate records? Note: I don't know VBA.



    Also tried adding PARAMETER = beginDateTime DateTime; This seems to return all records and assigns them all the date that the user was prompted for.



    Tried using DateValue in the parameter list:



    SELECT sampleID, DateValue(beginDateTime)
    FROM sample
    WHERE beginDateTime = [Enter sample date: ];


    This only returns dates = 0:00:00



    I'd like my query to prompt the user for a date (without a time) and return all records with that date along with their respective times.



    I would appreciate your help very much. Thanks in advance.










    share|improve this question


























      1












      1








      1








      Haven't found any closely related questions, so here goes.



      This is a simple version of my query:



      SELECT sampleID, beginDateTime
      FROM sample
      WHERE DateValue(beginDateTime) = [Enter sample date: ];


      This returns no records but should return 3 based on the date I entered.



      However, this version returns what I expect, all the records that match the supplied date and their respective times.



      SELECT sampleID, beginDateTime
      FROM sample
      WHERE DateValue(beginDateTime) = #2015-5-18#;


      How can I enable a user prompt that is properly formatted in Access SQL that will return the appropriate records? Note: I don't know VBA.



      Also tried adding PARAMETER = beginDateTime DateTime; This seems to return all records and assigns them all the date that the user was prompted for.



      Tried using DateValue in the parameter list:



      SELECT sampleID, DateValue(beginDateTime)
      FROM sample
      WHERE beginDateTime = [Enter sample date: ];


      This only returns dates = 0:00:00



      I'd like my query to prompt the user for a date (without a time) and return all records with that date along with their respective times.



      I would appreciate your help very much. Thanks in advance.










      share|improve this question
















      Haven't found any closely related questions, so here goes.



      This is a simple version of my query:



      SELECT sampleID, beginDateTime
      FROM sample
      WHERE DateValue(beginDateTime) = [Enter sample date: ];


      This returns no records but should return 3 based on the date I entered.



      However, this version returns what I expect, all the records that match the supplied date and their respective times.



      SELECT sampleID, beginDateTime
      FROM sample
      WHERE DateValue(beginDateTime) = #2015-5-18#;


      How can I enable a user prompt that is properly formatted in Access SQL that will return the appropriate records? Note: I don't know VBA.



      Also tried adding PARAMETER = beginDateTime DateTime; This seems to return all records and assigns them all the date that the user was prompted for.



      Tried using DateValue in the parameter list:



      SELECT sampleID, DateValue(beginDateTime)
      FROM sample
      WHERE beginDateTime = [Enter sample date: ];


      This only returns dates = 0:00:00



      I'd like my query to prompt the user for a date (without a time) and return all records with that date along with their respective times.



      I would appreciate your help very much. Thanks in advance.







      sql date ms-access prompt






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 13 '18 at 20:57









      jarlh

      29.3k52138




      29.3k52138










      asked Nov 13 '18 at 20:48









      AbbyAbby

      111




      111






















          3 Answers
          3






          active

          oldest

          votes


















          1














          Building on @Gustav's suggestion to use a typed parameter (which has the added benefit that Access will refuse a non valid date):



          PARAMETER [Enter sample date: ] DateTime;
          SELECT sampleID, beginDateTime
          FROM sample
          WHERE beginDateTime >= [Enter sample date: ] and beginDateTime < ([Enter sample date: ]+1)


          This way you avoid filtering on an expression, which disables index usage, and therefore would be slow on large datasets.




          Edit: To achieve this in the interface, just open your query in design view, then go to Design, Parameters, and enter the name and data type of your parameter(s).






          share|improve this answer

























          • StoneGiant's suggestion works. Why is it risky?

            – Abby
            Nov 14 '18 at 23:52











          • @Abby, Parameterized queries are safer than using string concatenation, because string concatenation is vulnerable to SQL Injection attack. SQL Injection is only a real concern if your database is publicly available. Since you were using an input box already, I just fixed your example. It is no more risky than what you had in place. It is a good habit to use parameterized queries, but not always absolutely necessary.

            – StoneGiant
            Nov 15 '18 at 3:13











          • @Abby: at the simplest level, the user can make a typo and enter a "non date" value, and then your CDate will fail. By defining your parameter as a date, any 'non date' will be refused. Not to mention the query will run faster.

            – Patrick Honorez
            Nov 15 '18 at 9:03


















          1














          Specify the parameter using the correct syntax:



          PARAMETERS [Enter sample date: ] DateTime;
          SELECT sampleID, beginDateTime
          FROM sample
          WHERE DateValue(beginDateTime) = [Enter sample date: ];


          Then it will accept a date entered as to the format of your current Windows settings.






          share|improve this answer




















          • 1





            +1 for suggestion to use a typed parameter. Not so great idea: filtering on an expression if very inefficient.

            – Patrick Honorez
            Nov 14 '18 at 9:39











          • So the suggestions that use PARAMETER and also include a user prompt return in prompting the user twice.

            – Abby
            Nov 15 '18 at 0:22











          • We have only your query, not how and where you use. The parameter will be prompted for once only.

            – Gustav
            Nov 15 '18 at 7:44


















          0














          You could try converting the value coming back from the input box to a date:



          SELECT sampleID, beginDateTime
          FROM sample
          WHERE DateValue(beginDateTime) = CDate([Enter sample date: ]);





          share|improve this answer























          • Tht's risky and for less efficient compared to @Gustav's answer

            – Patrick Honorez
            Nov 14 '18 at 9:35











          • Thanks, StoneGiant. Is there a way to incorporate this syntax into a query that's called by a form? Or is this off topic? I tried DateValue([sample.beginDateTime])=([Forms]![Lab Replicate Query Form]![date_time]) in the sql query. And added to the form that I want to run the query, in Control Source = CDate([beginDateTime]) but not luck. Any suggestions? Many thanks for your help.

            – Abby
            Nov 15 '18 at 0:30











          • I think that would be a new question with more details about what you're doing.

            – StoneGiant
            Nov 15 '18 at 3:09










          Your Answer






          StackExchange.ifUsing("editor", function ()
          StackExchange.using("externalEditor", function ()
          StackExchange.using("snippets", function ()
          StackExchange.snippets.init();
          );
          );
          , "code-snippets");

          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "1"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader:
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          ,
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













          draft saved

          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53289272%2faccess-sql-query-based-on-user-provided-date-only-returns-dates-with-times-00%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown

























          3 Answers
          3






          active

          oldest

          votes








          3 Answers
          3






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          Building on @Gustav's suggestion to use a typed parameter (which has the added benefit that Access will refuse a non valid date):



          PARAMETER [Enter sample date: ] DateTime;
          SELECT sampleID, beginDateTime
          FROM sample
          WHERE beginDateTime >= [Enter sample date: ] and beginDateTime < ([Enter sample date: ]+1)


          This way you avoid filtering on an expression, which disables index usage, and therefore would be slow on large datasets.




          Edit: To achieve this in the interface, just open your query in design view, then go to Design, Parameters, and enter the name and data type of your parameter(s).






          share|improve this answer

























          • StoneGiant's suggestion works. Why is it risky?

            – Abby
            Nov 14 '18 at 23:52











          • @Abby, Parameterized queries are safer than using string concatenation, because string concatenation is vulnerable to SQL Injection attack. SQL Injection is only a real concern if your database is publicly available. Since you were using an input box already, I just fixed your example. It is no more risky than what you had in place. It is a good habit to use parameterized queries, but not always absolutely necessary.

            – StoneGiant
            Nov 15 '18 at 3:13











          • @Abby: at the simplest level, the user can make a typo and enter a "non date" value, and then your CDate will fail. By defining your parameter as a date, any 'non date' will be refused. Not to mention the query will run faster.

            – Patrick Honorez
            Nov 15 '18 at 9:03















          1














          Building on @Gustav's suggestion to use a typed parameter (which has the added benefit that Access will refuse a non valid date):



          PARAMETER [Enter sample date: ] DateTime;
          SELECT sampleID, beginDateTime
          FROM sample
          WHERE beginDateTime >= [Enter sample date: ] and beginDateTime < ([Enter sample date: ]+1)


          This way you avoid filtering on an expression, which disables index usage, and therefore would be slow on large datasets.




          Edit: To achieve this in the interface, just open your query in design view, then go to Design, Parameters, and enter the name and data type of your parameter(s).






          share|improve this answer

























          • StoneGiant's suggestion works. Why is it risky?

            – Abby
            Nov 14 '18 at 23:52











          • @Abby, Parameterized queries are safer than using string concatenation, because string concatenation is vulnerable to SQL Injection attack. SQL Injection is only a real concern if your database is publicly available. Since you were using an input box already, I just fixed your example. It is no more risky than what you had in place. It is a good habit to use parameterized queries, but not always absolutely necessary.

            – StoneGiant
            Nov 15 '18 at 3:13











          • @Abby: at the simplest level, the user can make a typo and enter a "non date" value, and then your CDate will fail. By defining your parameter as a date, any 'non date' will be refused. Not to mention the query will run faster.

            – Patrick Honorez
            Nov 15 '18 at 9:03













          1












          1








          1







          Building on @Gustav's suggestion to use a typed parameter (which has the added benefit that Access will refuse a non valid date):



          PARAMETER [Enter sample date: ] DateTime;
          SELECT sampleID, beginDateTime
          FROM sample
          WHERE beginDateTime >= [Enter sample date: ] and beginDateTime < ([Enter sample date: ]+1)


          This way you avoid filtering on an expression, which disables index usage, and therefore would be slow on large datasets.




          Edit: To achieve this in the interface, just open your query in design view, then go to Design, Parameters, and enter the name and data type of your parameter(s).






          share|improve this answer















          Building on @Gustav's suggestion to use a typed parameter (which has the added benefit that Access will refuse a non valid date):



          PARAMETER [Enter sample date: ] DateTime;
          SELECT sampleID, beginDateTime
          FROM sample
          WHERE beginDateTime >= [Enter sample date: ] and beginDateTime < ([Enter sample date: ]+1)


          This way you avoid filtering on an expression, which disables index usage, and therefore would be slow on large datasets.




          Edit: To achieve this in the interface, just open your query in design view, then go to Design, Parameters, and enter the name and data type of your parameter(s).







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Nov 15 '18 at 9:01

























          answered Nov 14 '18 at 9:37









          Patrick HonorezPatrick Honorez

          18.9k564118




          18.9k564118












          • StoneGiant's suggestion works. Why is it risky?

            – Abby
            Nov 14 '18 at 23:52











          • @Abby, Parameterized queries are safer than using string concatenation, because string concatenation is vulnerable to SQL Injection attack. SQL Injection is only a real concern if your database is publicly available. Since you were using an input box already, I just fixed your example. It is no more risky than what you had in place. It is a good habit to use parameterized queries, but not always absolutely necessary.

            – StoneGiant
            Nov 15 '18 at 3:13











          • @Abby: at the simplest level, the user can make a typo and enter a "non date" value, and then your CDate will fail. By defining your parameter as a date, any 'non date' will be refused. Not to mention the query will run faster.

            – Patrick Honorez
            Nov 15 '18 at 9:03

















          • StoneGiant's suggestion works. Why is it risky?

            – Abby
            Nov 14 '18 at 23:52











          • @Abby, Parameterized queries are safer than using string concatenation, because string concatenation is vulnerable to SQL Injection attack. SQL Injection is only a real concern if your database is publicly available. Since you were using an input box already, I just fixed your example. It is no more risky than what you had in place. It is a good habit to use parameterized queries, but not always absolutely necessary.

            – StoneGiant
            Nov 15 '18 at 3:13











          • @Abby: at the simplest level, the user can make a typo and enter a "non date" value, and then your CDate will fail. By defining your parameter as a date, any 'non date' will be refused. Not to mention the query will run faster.

            – Patrick Honorez
            Nov 15 '18 at 9:03
















          StoneGiant's suggestion works. Why is it risky?

          – Abby
          Nov 14 '18 at 23:52





          StoneGiant's suggestion works. Why is it risky?

          – Abby
          Nov 14 '18 at 23:52













          @Abby, Parameterized queries are safer than using string concatenation, because string concatenation is vulnerable to SQL Injection attack. SQL Injection is only a real concern if your database is publicly available. Since you were using an input box already, I just fixed your example. It is no more risky than what you had in place. It is a good habit to use parameterized queries, but not always absolutely necessary.

          – StoneGiant
          Nov 15 '18 at 3:13





          @Abby, Parameterized queries are safer than using string concatenation, because string concatenation is vulnerable to SQL Injection attack. SQL Injection is only a real concern if your database is publicly available. Since you were using an input box already, I just fixed your example. It is no more risky than what you had in place. It is a good habit to use parameterized queries, but not always absolutely necessary.

          – StoneGiant
          Nov 15 '18 at 3:13













          @Abby: at the simplest level, the user can make a typo and enter a "non date" value, and then your CDate will fail. By defining your parameter as a date, any 'non date' will be refused. Not to mention the query will run faster.

          – Patrick Honorez
          Nov 15 '18 at 9:03





          @Abby: at the simplest level, the user can make a typo and enter a "non date" value, and then your CDate will fail. By defining your parameter as a date, any 'non date' will be refused. Not to mention the query will run faster.

          – Patrick Honorez
          Nov 15 '18 at 9:03













          1














          Specify the parameter using the correct syntax:



          PARAMETERS [Enter sample date: ] DateTime;
          SELECT sampleID, beginDateTime
          FROM sample
          WHERE DateValue(beginDateTime) = [Enter sample date: ];


          Then it will accept a date entered as to the format of your current Windows settings.






          share|improve this answer




















          • 1





            +1 for suggestion to use a typed parameter. Not so great idea: filtering on an expression if very inefficient.

            – Patrick Honorez
            Nov 14 '18 at 9:39











          • So the suggestions that use PARAMETER and also include a user prompt return in prompting the user twice.

            – Abby
            Nov 15 '18 at 0:22











          • We have only your query, not how and where you use. The parameter will be prompted for once only.

            – Gustav
            Nov 15 '18 at 7:44















          1














          Specify the parameter using the correct syntax:



          PARAMETERS [Enter sample date: ] DateTime;
          SELECT sampleID, beginDateTime
          FROM sample
          WHERE DateValue(beginDateTime) = [Enter sample date: ];


          Then it will accept a date entered as to the format of your current Windows settings.






          share|improve this answer




















          • 1





            +1 for suggestion to use a typed parameter. Not so great idea: filtering on an expression if very inefficient.

            – Patrick Honorez
            Nov 14 '18 at 9:39











          • So the suggestions that use PARAMETER and also include a user prompt return in prompting the user twice.

            – Abby
            Nov 15 '18 at 0:22











          • We have only your query, not how and where you use. The parameter will be prompted for once only.

            – Gustav
            Nov 15 '18 at 7:44













          1












          1








          1







          Specify the parameter using the correct syntax:



          PARAMETERS [Enter sample date: ] DateTime;
          SELECT sampleID, beginDateTime
          FROM sample
          WHERE DateValue(beginDateTime) = [Enter sample date: ];


          Then it will accept a date entered as to the format of your current Windows settings.






          share|improve this answer















          Specify the parameter using the correct syntax:



          PARAMETERS [Enter sample date: ] DateTime;
          SELECT sampleID, beginDateTime
          FROM sample
          WHERE DateValue(beginDateTime) = [Enter sample date: ];


          Then it will accept a date entered as to the format of your current Windows settings.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 13 at 18:10









          Santosh

          10.6k23059




          10.6k23059










          answered Nov 14 '18 at 9:27









          GustavGustav

          30.1k51936




          30.1k51936







          • 1





            +1 for suggestion to use a typed parameter. Not so great idea: filtering on an expression if very inefficient.

            – Patrick Honorez
            Nov 14 '18 at 9:39











          • So the suggestions that use PARAMETER and also include a user prompt return in prompting the user twice.

            – Abby
            Nov 15 '18 at 0:22











          • We have only your query, not how and where you use. The parameter will be prompted for once only.

            – Gustav
            Nov 15 '18 at 7:44












          • 1





            +1 for suggestion to use a typed parameter. Not so great idea: filtering on an expression if very inefficient.

            – Patrick Honorez
            Nov 14 '18 at 9:39











          • So the suggestions that use PARAMETER and also include a user prompt return in prompting the user twice.

            – Abby
            Nov 15 '18 at 0:22











          • We have only your query, not how and where you use. The parameter will be prompted for once only.

            – Gustav
            Nov 15 '18 at 7:44







          1




          1





          +1 for suggestion to use a typed parameter. Not so great idea: filtering on an expression if very inefficient.

          – Patrick Honorez
          Nov 14 '18 at 9:39





          +1 for suggestion to use a typed parameter. Not so great idea: filtering on an expression if very inefficient.

          – Patrick Honorez
          Nov 14 '18 at 9:39













          So the suggestions that use PARAMETER and also include a user prompt return in prompting the user twice.

          – Abby
          Nov 15 '18 at 0:22





          So the suggestions that use PARAMETER and also include a user prompt return in prompting the user twice.

          – Abby
          Nov 15 '18 at 0:22













          We have only your query, not how and where you use. The parameter will be prompted for once only.

          – Gustav
          Nov 15 '18 at 7:44





          We have only your query, not how and where you use. The parameter will be prompted for once only.

          – Gustav
          Nov 15 '18 at 7:44











          0














          You could try converting the value coming back from the input box to a date:



          SELECT sampleID, beginDateTime
          FROM sample
          WHERE DateValue(beginDateTime) = CDate([Enter sample date: ]);





          share|improve this answer























          • Tht's risky and for less efficient compared to @Gustav's answer

            – Patrick Honorez
            Nov 14 '18 at 9:35











          • Thanks, StoneGiant. Is there a way to incorporate this syntax into a query that's called by a form? Or is this off topic? I tried DateValue([sample.beginDateTime])=([Forms]![Lab Replicate Query Form]![date_time]) in the sql query. And added to the form that I want to run the query, in Control Source = CDate([beginDateTime]) but not luck. Any suggestions? Many thanks for your help.

            – Abby
            Nov 15 '18 at 0:30











          • I think that would be a new question with more details about what you're doing.

            – StoneGiant
            Nov 15 '18 at 3:09















          0














          You could try converting the value coming back from the input box to a date:



          SELECT sampleID, beginDateTime
          FROM sample
          WHERE DateValue(beginDateTime) = CDate([Enter sample date: ]);





          share|improve this answer























          • Tht's risky and for less efficient compared to @Gustav's answer

            – Patrick Honorez
            Nov 14 '18 at 9:35











          • Thanks, StoneGiant. Is there a way to incorporate this syntax into a query that's called by a form? Or is this off topic? I tried DateValue([sample.beginDateTime])=([Forms]![Lab Replicate Query Form]![date_time]) in the sql query. And added to the form that I want to run the query, in Control Source = CDate([beginDateTime]) but not luck. Any suggestions? Many thanks for your help.

            – Abby
            Nov 15 '18 at 0:30











          • I think that would be a new question with more details about what you're doing.

            – StoneGiant
            Nov 15 '18 at 3:09













          0












          0








          0







          You could try converting the value coming back from the input box to a date:



          SELECT sampleID, beginDateTime
          FROM sample
          WHERE DateValue(beginDateTime) = CDate([Enter sample date: ]);





          share|improve this answer













          You could try converting the value coming back from the input box to a date:



          SELECT sampleID, beginDateTime
          FROM sample
          WHERE DateValue(beginDateTime) = CDate([Enter sample date: ]);






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 13 '18 at 21:17









          StoneGiantStoneGiant

          912416




          912416












          • Tht's risky and for less efficient compared to @Gustav's answer

            – Patrick Honorez
            Nov 14 '18 at 9:35











          • Thanks, StoneGiant. Is there a way to incorporate this syntax into a query that's called by a form? Or is this off topic? I tried DateValue([sample.beginDateTime])=([Forms]![Lab Replicate Query Form]![date_time]) in the sql query. And added to the form that I want to run the query, in Control Source = CDate([beginDateTime]) but not luck. Any suggestions? Many thanks for your help.

            – Abby
            Nov 15 '18 at 0:30











          • I think that would be a new question with more details about what you're doing.

            – StoneGiant
            Nov 15 '18 at 3:09

















          • Tht's risky and for less efficient compared to @Gustav's answer

            – Patrick Honorez
            Nov 14 '18 at 9:35











          • Thanks, StoneGiant. Is there a way to incorporate this syntax into a query that's called by a form? Or is this off topic? I tried DateValue([sample.beginDateTime])=([Forms]![Lab Replicate Query Form]![date_time]) in the sql query. And added to the form that I want to run the query, in Control Source = CDate([beginDateTime]) but not luck. Any suggestions? Many thanks for your help.

            – Abby
            Nov 15 '18 at 0:30











          • I think that would be a new question with more details about what you're doing.

            – StoneGiant
            Nov 15 '18 at 3:09
















          Tht's risky and for less efficient compared to @Gustav's answer

          – Patrick Honorez
          Nov 14 '18 at 9:35





          Tht's risky and for less efficient compared to @Gustav's answer

          – Patrick Honorez
          Nov 14 '18 at 9:35













          Thanks, StoneGiant. Is there a way to incorporate this syntax into a query that's called by a form? Or is this off topic? I tried DateValue([sample.beginDateTime])=([Forms]![Lab Replicate Query Form]![date_time]) in the sql query. And added to the form that I want to run the query, in Control Source = CDate([beginDateTime]) but not luck. Any suggestions? Many thanks for your help.

          – Abby
          Nov 15 '18 at 0:30





          Thanks, StoneGiant. Is there a way to incorporate this syntax into a query that's called by a form? Or is this off topic? I tried DateValue([sample.beginDateTime])=([Forms]![Lab Replicate Query Form]![date_time]) in the sql query. And added to the form that I want to run the query, in Control Source = CDate([beginDateTime]) but not luck. Any suggestions? Many thanks for your help.

          – Abby
          Nov 15 '18 at 0:30













          I think that would be a new question with more details about what you're doing.

          – StoneGiant
          Nov 15 '18 at 3:09





          I think that would be a new question with more details about what you're doing.

          – StoneGiant
          Nov 15 '18 at 3:09

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid


          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.

          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53289272%2faccess-sql-query-based-on-user-provided-date-only-returns-dates-with-times-00%23new-answer', 'question_page');

          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Use pre created SQLite database for Android project in kotlin

          Darth Vader #20

          Ondo