Hall of Fame

1. capricorn12,136,854
2. DatabaseMX1,791,758
3. LSMCons...1,256,766
4. boag20001,036,189
5. peter57r799,346
6. matthews...688,896
7. rockiroads574,427
8. thenelson445,637
9. GRayL434,146
10. TextReport434,053
11. puppydog...400,608
12. tbsgadi367,274
13. JDettman322,461
14. cactus_d...281,926
15. mbizup243,682
16. jimpen211,515
17. harfang207,824
18. GrahamM...183,618
19. Helen_Fe...177,740
20. LPurvis165,663
21. angelIII146,835
22. hnasr137,021
23. kelvinsparks136,703
24. Tramtrak136,379
25. mildurait128,151

1. capricorn113,063,646
2. DatabaseMX6,134,612
3. rockiroads6,047,347
4. nico50385,705,281
5. LSMCons...5,307,939
6. peter57r5,070,812
7. LPurvis3,627,703
8. harfang3,312,263
9. shanesue...3,288,317
10. GRayL3,271,116
11. stevbe2,861,511
12. jimhorn2,807,017
13. boag20002,733,425
14. matthews...2,521,203
15. mbizup2,374,174
16. thenelson2,146,006
17. flavo2,117,383
18. jadedata1,968,277
19. jefftwilley1,887,172
20. puppydog...1,849,966
21. cactus_d...1,681,384
22. eghtebas1,534,843
23. JDettman1,468,976
24. jjafferr1,340,995
25. dannywar...1,329,637

	[x] Posted via EE Mobile
	Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question

	[x] Attachment Details

[x]

The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

The Grade of the Solution
The Zone Rank of the Expert Providing the Solution
The Number of Author and Expert Comments
The Number of Experts Contributing
The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

5.8

3 failed attempts rule - failed

Asked by billcute in Microsoft Access Database

Tags: attemps, current, dateadd, fail, rule

The following code was recently worked on....but I believe it still need some tweaking....
if user enters an invalid date in frmGetdateFiling.txtGetdateFiling, I recieved an Invalid date msgbox,
hoever the code is expected to give me 3 other attempts before shutting down db..this is not havppening.

Instead I get a message that I have no attempt left even though user has only invalid date once. How do I correct this?
' *************
'Title for message boxes, change as u see fit
Private Const FRM_TITLE = "Filing Date"

'Define the number of days for your grace period here
Private Const GRACE_PERIOD = 14

'Define the max number of attemps possible
Private Const MAX_FAILED_ATTEMPTS = 3

'This variable is used to record the number of times the date entered is invalid
Dim m_iNoAttempts As Integer

Public Function GracePeriodValidation(ByVal dValDate As Date, ByVal iQQ As Integer, ByVal iYY As Integer) As Boolean

Dim iGracePeriod As Integer
Dim dLastDate As Date
Dim dCheckDate As Date

'Get the quarter to file. If quarter 1 then for previous quarter, we need to subtract the year also
'Here we define the grace period
'It might be useful if u define is 14 as a constant
'or store it in sum lookup table
iGracePeriod = GRACE_PERIOD

'Get last date, calculated using DateSerial
'Pass in current year, then month is calculated by multiplying current quarter by 3
'then we add 1, so we end up the following month
'the last parameter is 0, which means we take away one day
'thus giving us the last day of the previous month i.e. end of quarter
dLastDate = DateSerial(iYY, (iQQ * 3) + 1, 0)

'Check current date is within the filing date period
'Return false if invalid, TRUE otherwise
If dValDate < dLastDate Or dValDate > DateAdd("d", GRACE_PERIOD + 1, dLastDate) Then '<<-- I changed this line from 14 to 15
GracePeriodValidation = False
Else
GracePeriodValidation = True
End If

End Function

View the Solution FREE for 30 Days

20091111-EE-VQP-92

3 failed attempts rule - failed

Asked by billcute in Microsoft Access Database

Tags: attemps, current, dateadd, fail, rule

About this solution