|
|
| Submitted on: 5/14/1999
By: Preston Smith
Level: Not Given
User Rating:
By 102 Users
Compatibility:VB 5.0, VB 6.0
Users have accessed this code 6333 times.
| |
| | | This program test the Visual Basic program you are currently running. As you will see.
| |
| |
|
code:
Can't Copy and Paste this?
Click here for a copy-and-paste friendly version of this code!
Terms of Agreement:
By using this code, you agree to the following terms...
1) You may use
this code in your own programs (and may compile it into a program and distribute it in compiled format for languages that allow it) freely and with no charge.
2) You MAY NOT redistribute this code (for example to a web site) without written permission from the original author. Failure to do so is a violation of copyright laws.
3) You may link to this code from another website, but ONLY if it is not wrapped in a frame.
4) You will abide by any additional copyright restrictions which the author may have placed in the code or code's description. |
'**************************************
' Name: Y2K Test for VB5 and 6
' Description:This program test the Visu
' al Basic program you are currently runni
' ng. As you will see.
' By: Preston Smith
'
' Assumes:You can adjust the dates for J
' an 1st 1930, Jan 1st 2029, Jan 1st 00 an
' d Feb 29 or 30 2000. To see if your vers
' ion is compliant then you should use 1/1
' /00 for the year 2000, and 2/29/00 for t
' he Leap Year date (this will cause a run
' -time error, if NOT compliant). I made a
' big mistake before, the date regarding t
' he leap year, should not cause a run tim
' e error if it is compliant.
'
' Side Effects:If you set up the code to
' check for the leap year date you should
' have a run-time error. If you do NOT hav
' e an error that is good. If you actually
' see a date then your version of VB is no
' t compliant with Y2K. The updates and pa
' tches may be available at microsoft's MS
' DN websight. Problems? Get the SP3 updat
' es, Go here (VB6): http://msdn.microsoft
' .com/vstudio/sp/default.asp Go here (VB5
' ): http://msdn.microsoft.com/vstudio/sp/
' vs97/default.asp
'
'This code is copyrighted and has' limited warranties.Please see http://w
' ww.Planet-Source-Code.com/vb/scripts/Sho
' wCode.asp?txtCodeId=1776&lngWId;=1'for details.'**************************************
Sub Form_Load()
Dim MyDate as Date
MyDate = "1/1/00" 'Or
'MyDate = "1/1/29" 'Returns 1/1/2029
'MyDate = "1/1/30" 'Returns 1/1/1930
'MyDate = "2/29/00" 'The Leap Year Date
' (Usually causes the most probs)
MsgBox Format(MyDate, "mm/dd/yyyy")
End Sub
| |
Other 1 submission(s) by this author
|
|
| |
| Report Bad Submission |
|
| |
| Your Vote! |
|
See Voting Log |
| |
| Other User Comments |
5/14/1999 12:05:00 PM:Craig
Is the runtime error because there
never is a Feb. 30th? Should be Feb.
29th on a leap year?
|
5/19/1999 10:31:00 PM:ARRiVE
Yes That is the compiler catching it at
runtime depending on prefs. Or it is a
type mismatch on run time. the 29th is
a leap a year! no wonder we have so
many Y 2 K issues =\
|
5/20/1999 12:33:00 PM:Preston Smith
Ooops. The date should be 2/29/00 to
test for the leap year. I will fix
that. The error is a Type Mismatch
regardless of the date. Either way, if
there is know error, then there is
something wrong with VB. Otherwise, if
you get the Mismatch error, then there
is nothing wrong with the code.
|
6/9/1999 7:18:00 PM:Jargalsaikhan.B
Thanks for your free source!
|
6/9/1999 9:33:00 PM:Jean
Good job Preston looks like you'll be
helping me next year!
|
6/10/1999 8:30:00 AM:ed
The year 2000 is a leap year so there
should be no error when running the
last test
|
6/11/1999 12:19:00 AM:Rob
Well i have VS6.0 SP3 and i get no
error, am i missing something
here?
hehe thanx
|
6/20/1999 3:59:00 PM:
I have the same problem as Rob, but i'm
using VB 5.0
|
6/20/1999 4:09:00 PM:Drunk_Cowboy
Im running VB5 what can you do to fix
your VB if you don't get an error ?
|
6/25/1999 3:05:00 AM:
Basic, but Good
|
7/6/1999 5:39:00 PM:Bill
To fix VB you would have to get into
the source code of VB and fix it. That
means you can't fix it.
|
7/6/1999 9:50:00 PM:Preston
From what I read at MSDN online, the
Y2K problem can be repaired by
installing the SP3 Updates. Of course,
this is Microsoft were talking about.
I had an error with VB6.0. I don't
have the mismatch error anymore after
installing the patch.
|
7/9/1999 7:42:00 PM:Beth Develos
Thanks for the code...
|
8/1/1999 6:57:00 PM:Dan
We Have an old (not updated) version of
VB5 but we updated Win 98 with Y2K
Fix
No problem with any of your code
including my own little
addition:
MsgBox Format(MyDate + 1,
"mm/dd/yyyy")
on the leap year that
shows the correct 03/01/2000 date.
|
|
| Add Your Feedback! |
Note:Not only will your feedback be posted, but an email will be sent to the code's author in your name.
NOTICE: The author of this code has been kind enough to share it with you. If you have a criticism, please state it politely or it will be deleted.
For feedback not related to this particular code, please click here.
|
|
