Home All Groups Group Topic Archive Search About

InputBox problems after upgrade

Author
10 Jul 2006 5:55 PM
jpoquette
I have recently upgraded a Visual Basic 2003 win forms application to
2005.  After doing so I can no longer get my project to compile.  The
code is bombing on any line that uses an InputBox.  I'm getting a
MissingManifestResourceException unhandled Exception.

I've read several postings and tried various things, but I can not get
anything to work.  I've also created a new 2005 project from scratch,
added an InputBox in code, and I still receive the same error.

Does anyone know how to fix this situation?

Your help is greatly appreciated!!

Author
10 Jul 2006 6:34 PM
Samuel Shulman
There is one simple solution and that's to implement one yourself it is not
too difficult and I can send you some source code

hth,
Samuel Shulman

<jpoque***@mileskimball.com> wrote in message
Show quoteHide quote
news:1152554104.573485.59950@75g2000cwc.googlegroups.com...
>I have recently upgraded a Visual Basic 2003 win forms application to
> 2005.  After doing so I can no longer get my project to compile.  The
> code is bombing on any line that uses an InputBox.  I'm getting a
> MissingManifestResourceException unhandled Exception.
>
> I've read several postings and tried various things, but I can not get
> anything to work.  I've also created a new 2005 project from scratch,
> added an InputBox in code, and I still receive the same error.
>
> Does anyone know how to fix this situation?
>
> Your help is greatly appreciated!!
>
Author
11 Jul 2006 12:38 PM
Samuel Shulman
I tried sending you the source but you email server rejected it as 'Unsafe'



Show quoteHide quote
"Samuel Shulman" <samuel.shul***@ntlworld.com> wrote in message
news:O45Y%239EpGHA.1592@TK2MSFTNGP04.phx.gbl...
> There is one simple solution and that's to implement one yourself it is
> not too difficult and I can send you some source code
>
> hth,
> Samuel Shulman
>
> <jpoque***@mileskimball.com> wrote in message
> news:1152554104.573485.59950@75g2000cwc.googlegroups.com...
>>I have recently upgraded a Visual Basic 2003 win forms application to
>> 2005.  After doing so I can no longer get my project to compile.  The
>> code is bombing on any line that uses an InputBox.  I'm getting a
>> MissingManifestResourceException unhandled Exception.
>>
>> I've read several postings and tried various things, but I can not get
>> anything to work.  I've also created a new 2005 project from scratch,
>> added an InputBox in code, and I still receive the same error.
>>
>> Does anyone know how to fix this situation?
>>
>> Your help is greatly appreciated!!
>>
>
>
Author
11 Jul 2006 6:22 PM
jpoquette
I was able to retrieve you attachment from our email server, so I'm
going to try it now and see how it works.
Author
10 Jul 2006 8:50 PM
Terry
Hi,
I just tried using the InputBox function and it works fine.  What do you
mean by "added an InputBox in code"?   Can you post some code from the new
project that shows the problem?
--
Terry


Show quoteHide quote
"jpoque***@mileskimball.com" wrote:

> I have recently upgraded a Visual Basic 2003 win forms application to
> 2005.  After doing so I can no longer get my project to compile.  The
> code is bombing on any line that uses an InputBox.  I'm getting a
> MissingManifestResourceException unhandled Exception.
>
> I've read several postings and tried various things, but I can not get
> anything to work.  I've also created a new 2005 project from scratch,
> added an InputBox in code, and I still receive the same error.
>
> Does anyone know how to fix this situation?
>
> Your help is greatly appreciated!!
>
>
Author
11 Jul 2006 6:37 PM
jpoquette
Here's a code sample.  It errors out when it hits the line with the
InputBox

Public Sub msMailDate(ByRef Quit As Boolean)

'*****************************************************************
        'Author         XXX
        'Date Created   5/23/2005
        'Purpose        Used to change mail date

'*****************************************************************
        Dim sMailDate As String
        Dim bIsDate As Boolean = False
        Do Until bIsDate = True

            sMailDate = InputBox("Please enter the mail date", "Mail
Date", Date.Now)

            If IsDate(sMailDate) Then
                dtMailDate = CDate(sMailDate)
                Me.StatusBarPanel1.Text = "Mail Date " &
dtMailDate.Date
                bIsDate = True
            ElseIf sMailDate = "" Then
                Quit = True
                Exit Sub
            ElseIf Not (IsDate(sMailDate)) Then
                bIsDate = False
            End If
        Loop
    End Sub
Author
11 Jul 2006 6:56 PM
Al Reid
Try changing the "Date.Now" to "Date.Now.ToShortDateString"  since the InputBox default is looking for a string not a date.

--
Al Reid

Show quoteHide quote
<jpoque***@mileskimball.com> wrote in message news:1152643045.600969.268620@p79g2000cwp.googlegroups.com...
> Here's a code sample.  It errors out when it hits the line with the
> InputBox
>
>  Public Sub msMailDate(ByRef Quit As Boolean)
>
> '*****************************************************************
>         'Author         XXX
>         'Date Created   5/23/2005
>         'Purpose        Used to change mail date
>
> '*****************************************************************
>         Dim sMailDate As String
>         Dim bIsDate As Boolean = False
>         Do Until bIsDate = True
>
>             sMailDate = InputBox("Please enter the mail date", "Mail
> Date", Date.Now)
>
>             If IsDate(sMailDate) Then
>                 dtMailDate = CDate(sMailDate)
>                 Me.StatusBarPanel1.Text = "Mail Date " &
> dtMailDate.Date
>                 bIsDate = True
>             ElseIf sMailDate = "" Then
>                 Quit = True
>                 Exit Sub
>             ElseIf Not (IsDate(sMailDate)) Then
>                 bIsDate = False
>             End If
>         Loop
>     End Sub
>
Author
11 Jul 2006 7:46 PM
jpoquette
Actaully it doesn't matter what I pass in or expect out, anything fails
to execute.
Author
11 Jul 2006 9:12 PM
jpoquette
My fix was to move my solution to my hard drive instead of running it
off a network drive.  I'm going to do a little more research on why
this is, but it boils down to security when trying to execute an
assembly that is not on your hard drive.