Visual Basic and T-SQL Server will not correlate in the date time understanding.
Example:
When you are updating a date field in the cBiz
Data base through T-SQL.
INSERT
INTO
Requirements
(ReqIntID,ReqID,NumberOfOpenings,UserIDs,LinkToIntID,CreateDate,EditDate)
VALUES
(@CurCountNEW1,dbo.GenerateReqID(@CurCountNEW1),N'1',N',Admin,',@ContactIntID,GETDATE(),GETDATE()
)
There is a bug in the Visual
Basic for given date time it will consider
upper limit of seconds. The following images are
of same record from cBiz View and SQL server
View.
SQL Server
will consider the Lower Limit of seconds.
Solution:
when we
update the date field from out side the cBiz,
then convert it to Small Date Time and Update it.
INSERT
INTO
Requirements
(ReqIntID,ReqID,NumberOfOpenings,UserIDs,LinkToIntID,CreateDate,EditDate)
VALUES
(@CurCountNEW1,dbo.GenerateReqID(@CurCountNEW1),N'1',N',Admin,',@ContactIntID,CAST(GETDATE()
AS
SMALLDATETIME),CAST(GETDATE()
AS
SMALLDATETIME))
