InputBox problems after upgrade

J

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!!
 
S

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
 
G

Guest

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?
 
J

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.
 
J

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
 
A

Al Reid

Try changing the "Date.Now" to "Date.Now.ToShortDateString" since the InputBox default is looking for a string not a date.
 
J

jpoquette

Actaully it doesn't matter what I pass in or expect out, anything fails
to execute.
 
J

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.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top