IIRC the only way to extend the shell's context menu is through COM. You would have to do pretty much the same as you did in VB6, writting the DLL, registering it etc.
SMTP has a VRFY command which can be used to test if an e-mail address is valid for the system, however it is nearly always turned off as it makes it easy for spammers to collect valid addresses.
more details can be found here http://www.cotse.com/CIE/RFC/821/6.htm
relying on a '.' followed by 3 characters may not be safe if they could also type non-executables .js .pl etc. for the executable.
The two textboes suggestion is probably the easiest although you may want to mimic earlier versions of windows and if the path can contain spaces require the users to enclose it in quotes
i.e.
"C:\Program Files\myapp\test.exe" /r /t"
that way you can look for the first and second double quotes and everything between them is the executable. Everything else is arguments to the executable.
Could be a problem with dependencies of the .OCX - is this problem machine running a different OS, ServicePack, Office, IE or any other radically different software?
What does the Check_Files function do? Is there any code handling the CurrentDir event?
Just pasted your code into a new project and commented out the raiseevent line and simple made a dummy Check_files function that just did a Debug.WriteLine of the file name and it worked fine on my local drives.
How deep are the recursions going?
The form has a AcceptButton property - have a play and you'll see what I mean.
http://www.xtremedotnettalk.com/showthread.php?s=&threadid=76208&highlight=form+show+hide
http://www.xtremedotnettalk.com/showthread.php?s=&threadid=70825&highlight=form+show+hide
not sure on the winsock one - are you using the winsock control?
just put it once - all your sample is doing is adding 100 to the value.
something like
if pb.Value + 10 < pb.Maximum
pb.Value += 10
else
pb.Value = pb.Maximum
end if
should do the trick
You may have more sucess using the native .Net ListView control rather than goig through interop to the VB6 COM control.
Is this a result of usig the migration wizard?
very low level code.
however a quiick search on google brought back this - may be of some use may not...
http://www.codeguru.com/vb/comments/1170.shtml
You can get this error if you are keeping lots of file handles open. In task manager on the proces view you can get it to display the handles (view - select columns). Is the number of handles getting very large?
Not sure if Access does suppor them or not either. You may want to investigate MSDE from Microsoft which gives you a SQL server compliant engine - works well with access as a front end.
If you are concatenating strings use & instead of + as + is a mathematical operator that can double as a string operator - this could be causing the problem.
A better way would be to use server side stored procedures - search these forums and MSDN for a lot more information on Stored Procedures.
If you are disposing of them while going forwards then I think the internal numbers are being moved down by one everytime you delete something. Starting at the top and working down prevents you skipping over them in this way.