Failed to compare dates in a stored process?

Since the stored procedure gets the correct result, the problem is definitely not the stored procedure's problem;

Try to check the part of the system you are developing that binds the data source, check the process, for example, you can first set a breakpoint on the statement that binds the datagrid data source to see if the value of the data source is the required value. Then if it is, start trying to run the checks step by step in the program, and you'll know. The main thing is that I don't know what system you developed with, otherwise you can give better advice.

The stored procedure does not return a dataset.

So the datagrid you bind won't have data.

You can try to write it as a function.

create function [dbo].[function name]startdate datetime, @enddate datetime

returns table

asreturn

select *

from yhzh

where paybackdate>@startdate and paybackdate<@enddate)

Gosql Enter select * from function name ('12/31/2009', '12/31/2010'）

Although I'm not familiar with C, the sentence upstairs that the stored procedure does not return the result set is wrong, and the owner's process returns the result set.

In SQL Server, you need to add " to the date value'Such as:

down_list_update 3," & tdate & "," & cint(request("id")))

Instead:"down_list_update 3,'" & tdate & "'," & cint(request("id")))

Your string doesn't meet the date format, and there's a problem with the conversion.

If it is a character type, add extra single quotation marks to the concatenation.

set @s = 'select top 10 * from t_position where adddate<'''+@t+''''

Only compare"Hours, minutes, seconds"part of the words.

Directly to char(Date 1,'hh24miss'>to char(date 2,'hh24miss')

This way to compare.

If you want to compare dates, then directly.

Date 1 > Date 2

This way to compare.

Enter the formula =today() in excel.

There are many issues to be aware of.

Depending on what you're inserting, if you don't need things, I recommend using @@raiserror system-defined global variables to increase the level of error messages, so that inserting errors is more intuitive!

Enter show error to see ** is wrong;

update fang_product

set fang_ = ,fang_ = 0

where uuid = ;

goto nextrow;

Can the update statement be used like this?

Add a comma to one field and another field.

Did you get an error when you executed it?

The error is basically that the column does not exist in the selected table, and SAP acknowledges the status. Distinguish between votes, are these listings existing or garbled? If the actual column name is this suggestion, for each table, the column is in parentheses, [SAP Join Admit Status].

Ticket distinction] in this way.

See Chinese, this should be noted in the oracle. Don't use Chinese fields.