User1216627406 posted
I don't understand your response. Why can't you replace the row visibility logic with setting the CSS? If the Visibility logic works then I do not understand why setting the display property is any
different.
Yea, you have a good point there. This issue though is not the visibility is not being set to hidden. The issue is that when I click to add a new row, it does not add one/
In other words, even though setting the visibility to none works, when attempting to click the button to add a new row, it is not doing that.
So, I can try your suggestion but not sure if that solves the click button problem.
Secondly, the empty GridView rows are expected and this page has behaved this way since 2016? I though the empty row were unwanted?
No, what I meant was that the page was working perfectly until I made the change.
In other words, normally, you get one empty row by default and you could add additional rows if needed and that row would be added. It has been working that way until I made the change in the event click method that
I posted today. Then it stopped adding the additional rows.
I will post the stored proc shortly. It is on my other laptop.
Here is the stored procedure:
I am sure you understand what it is doing but for vanity, it checks three things:
1, when a user attempts to submit a form, has this user submitted the form this year already? 0 for no, 1 yes
2, did this user submit this form last year? 0 for no, 1 for yes
3, did this year submit this form previous years (not this year, not last year but any year before last year? 0 for no, 1 for years.
On my VB, if thisYear = 1, then the user submitted this form already; cannot submit again. Let the user know this with a message.
This works great.
If user submitted this form last year or year before last, grab the record s/he submitted and populate the gridview form.
This is where the issue comes in.
If the user did the form last year or the year before and his/her record populates the gridview and one of the controls has more than one row, then the rest have more than one row whether empty or not.
ALTER PROCEDURE [dbo].[uspGetRecs]
@empID nvarchar(50)
AS
begin
SELECT s.sourcename, s.sourceaddress,d.dateCreated,sp.spousename, sp.spouseaddress,
r.reimbursementName,r.reimbursementAddress, h.HonorariaName,h.HonorariaAddress,
h.HonorariaName as honoraria,h.HonorariaAddress,h.HonorariaIncome,g.giftName,g.giftAddress,dv.dividentName,dv.dividentAddress,
o.orgName,o.orgAddress,cr.creditorName, cr.creditorAddress,
CASE WHEN d.dateCreated < prev_yr_jan01 THEN 1 ELSE 0 END AS pastYears,
CASE WHEN d.dateCreated >= prev_yr_jan01 AND d.dateCreated < curr_yr_jan01
THEN 1 ELSE 0 END as previousYear,
CASE WHEN d.dateCreated >= curr_yr_jan01 THEN 1 ELSE 0 END as thisYear
FROM Employees e
CROSS APPLY (
SELECT DATEADD(YEAR, DATEDIFF(YEAR, 0, GETDATE()), 0) AS curr_yr_jan01,
DATEADD(YEAR, DATEDIFF(YEAR, 0, GETDATE()) - 1, 0) AS prev_yr_jan01
) AS yr_start_dates
INNER JOIN SourceDetails s ON e.EmployeeID = s.EmployeeID
INNER JOIN SpouseDetails sp ON e.EmployeeID = sp.employeeID
INNER JOIN DividentDetails dv ON e.EmployeeID = dv.EmployeeID
INNER JOIN ReimbursementDetails r ON e.EmployeeID = r.employeeID
INNER JOIN Honoraria h ON e.EmployeeID = h .EmployeeID
INNER JOIN GiftDetails g ON e.EmployeeID = g.employeeID
INNER JOIN dateDetails d ON e.EmployeeID = d.employeeID
INNER JOIN org o ON e.employeeID = o.employeeID
INNER JOIN creditorDetails cr ON e.employeeID = cr.employeeID
WHERE e.EmpID=@empID
ORDER By d.dateCreated DESC
end
As you can see, 8 tables are being joined by employeeID since that is the common key amongst them.
Sometimes, I wonder if I just do this check one table at a time instead of joining them, would that have made any difference?
Reason I have not tried this theory is not sure how to use the stored proc on my VB
Thanks
