This is the declaration of the Public Sub:
Public Sub InitializeForm(ByVal strContractCode As String, ByVal lngUnitID As Long, _
ByVal strUnitCode As String, ByVal strPropertyName As String)
I have changed this declaration into the following because I need to pass 2 new parameters:
Public Sub InitializeForm(ByVal strContractCode As String, ByVal lngUnitID As Long, _
ByVal strUnitCode As String, ByVal strPropertyName As String, _
Byal dtVoucherDate As Date, ByVal lngVoucherID As Long)
During the compilation for new .exe file I found out that there are more places where this function is caled from but I can not provide values for these 2 new parameters. The compiler told me that "value is not optional" when the refermce to this function was discovered.
I decided to fix this by making the following change into the call of this Public Sub:
Public Sub InitializeForm(ByVal strContractCode As String, ByVal lngUnitID As Long, _
ByVal strUnitCode As String, ByVal strPropertyName As String, _
Optional dtVoucherDate As Date, Optional lngVoucherID As Long)
The compiler recompiled and built the new .exe for me.
Please tell me if this fix resolved my issue or there are still a risk within this application that if this Public Sub is called from somwhere I was not able to find I may have an unhandled break?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: angelIIIPosted on 2009-11-05 at 13:05:59ID: 25754022
as long as you "handle" inside the sub the "optional" parameters, it should be fine.
usually, you specify a explicit default value, which is set when indeed no value is specified:
Public Sub InitializeForm(ByVal strContractCode As String, ByVal lngUnitID As Long, _
ByVal strUnitCode As String, ByVal strPropertyName As String, _
Optional dtVoucherDate As Date = empty, Optional lngVoucherID As Long = -1)