|
Shazz Rock wrote: Shell "C:\shashi\test.doc"
Error: Invalid procedure call or argument
There's only a couple of reasons this would have failed. The first is if the file path doesn't exist. The second is if there is a problem with the extension association (.doc) with an application. But, in this case, you would not have gotten the error you did.
Shazz Rock wrote: Shell "C:\Program Files\Microsoft Office\OFFICE11\winword.exe" & "C:\shashi\test.doc"
Error: File Not Found
It didn't work because you tried to execute something called Program, with the command line parameters of Files\Microsoft and Office\OFFICE11\winword.exe and C:\shashi\test.doc. Spaces, anywhere in the command line, are treated as delimiters.
You need to wrap full path specifications in double quotes so they are treated as a single component of the command line.
Your code should be closer to:
Shell """C:\Program Files\Microsoft Office\OFFICE11\winword.exe"" & _
" " & """C:\shashi\test.doc"""
|
|
|
|
|
"hello
I have following problem, I want to pass a variable in VBA code (MS Access)
M_Variable = "Text"
with Mrst
![M_Variable]= "AnotherTextString"
end with
The problem is I don't know how to pass this variable on.
Do I have to put hyphens? ("'"M_Variable"'" or [ & "'" & M_Variable & & "'" & ]) I tried some more combinations but they didn't work.
Many thanks for your help
Pierre
|
|
|
|
|
Try this
dim x as string
x = Mrst![M_Variable]
Bob
Ashfield Consultants Ltd
|
|
|
|
|
Hello Bob
Thank you for your reply.
It gave me a hint. following solution worked.
With MyRst
.AddNew
.Fields(MyString) = mychaine(M_Number)
.Update
End With
Thanks again
Pierre
|
|
|
|
|
No problem.
Bob
Ashfield Consultants Ltd
|
|
|
|
|
i thought it is not very difficult to create such a fn
|
|
|
|
|
Please try to reply to the post, not create a new one.
WEB2BABA wrote: i thought it is not very difficult to create such a fn
Probably not. Try researching the answer you were given.
Bob
Ashfield Consultants Ltd
|
|
|
|
|
Hi there
I have a problem, can you help me.
When I find some code in VB6 and opens it in Visual Studio 2008 I get a an error I can't find out?
Like this :
TextBox3.Text = VB6.Format(Hex(colr), "0#####")
<b>VB6????? what should I write instead of "VB6" in visual Studio 2008? </b>
|
|
|
|
|
Don't open VB6 code in Visual Studio 2008. Use Notepad, or Visual Studio 6.
|
|
|
|
|
Why are you even doing this?? You can't compile VB6 in Visual Studio 2008.
|
|
|
|
|
Simon give me a hint in another section. But Visual 2008 can help you compile or translate your vb6 code. It doesn't do it very good, by save some time, but 2008 ´reads many thing diffents than vb6 (or .net code) I'm new at this 
|
|
|
|
|
vbMr'J wrote: but 2008 ´reads many thing diffents than vb6 (or .net code)
That doesn't make any sense at all... There is a VB6 Migration Wizard that will convert your VB6 project and code to something resembling VB.NET code, but it really does just wrap your VB6 code in a kind of emulator that lets your old VB6 code (converted to VB.NET equivilent code) run. It's by no means a perfect solution and there is no product out there that will do a perfect conversion, other than recoding the entire project by hand.
|
|
|
|
|
I am making a application in vb.net .
I need a VB.NET function that will move the mouse cursor relative to an external application(eg-note pad or paint or a game) such as at X: 200, Y:150. However, I need these coordinates to be relative to the external application window, not for the user's screen. I want to create such function.plz help.
|
|
|
|
|
You'll have to write the function yourself. There is no support for this in the .NET Framework.
Are you familiar with Windows internals and how windows and mouse messages work?
|
|
|
|
|
Is it possible to force a property some how in VB.NET.(For a form) One way I could do this is to use a parameter in the constructor and delete the default constructor, but from what I have been told you are not supposed to modify the windows generated code. I am a noob with properties so any help would be appreciated. BTW the reason I am trying to do all of this is because if we do not have a parameter passed to this form when it is opened then it will not work properly and I would like to make it so that if we call this form without passing that property the compiler generates and error.
Humble Programmer
|
|
|
|
|
You should look at the "New" sub.
If you put code like the following, then everytime you create an instance the form, all parameters will be required:
Public Sub New(Param as String)
Blah
Blah
End Sub
Does this work with forms? I think so.
|
|
|
|
|
Would this not be considered modifying windows generated code? Also the new is the constructor is that correct?
Humble Programmer
|
|
|
|
|
Yes, the New sub is the constructor. You are only adding an additional overloaded constructor which takes the parameters you need. If you want to ensure that only your contructor can be called (and not the default parameterless one) you can make the default constructor be a private function.
Scott Dorman Microsoft® MVP - Visual C# | MCPD
President - Tampa Bay IASA
[ Blog][ Articles][ Forum Guidelines]
Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
|
|
|
|
|
But again would that not be modifying form generated code by changing the New sub to be Private?
Humble Programmer
|
|
|
|
|
No, it's not. There are also pitfalls do removing the New() method, as I've descrbied in my other post.
The designer generated code sits in a #Region block specifically designated as "designer generated".
|
|
|
|
|
As far as I can tell, when you create a new class that inherits from System.Windows.Forms.Form, Visual Studio will not automatically generate a default (parameterless) constructor in the code. The direct answer to your question is that, since the code does not already contain a default (parameterless) constructor, adding a new private default constructor is not changing generated code.
Scott Dorman Microsoft® MVP - Visual C# | MCPD
President - Tampa Bay IASA
[ Blog][ Articles][ Forum Guidelines]
Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
|
|
|
|
|
Whoops! My bad.
[Edit] Actually, it's in the base Form class. But, you can't remove it if you want the form to show up in the designer. The designer uses only the parameterless constructor to create an instance of the form to show on the design surface. Removing it kills the ability to design the form.
|
|
|
|
|
Hmmm...I actually created a blank VB WinForms project and didn't see any constructors, even in the designer generated file (Form1.Designer.vb). I do see it if I look at the compiled code with Reflector.
Yes, I found that if I created my own private default constructor the code wouldn't compile, throwing errors in the Application.Designer.vb file.
Scott Dorman Microsoft® MVP - Visual C# | MCPD
President - Tampa Bay IASA
[ Blog][ Articles][ Forum Guidelines]
Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai
|
|
|
|
|
Scott Dorman wrote: Hmmm...I actually created a blank VB WinForms project and didn't see any constructors, even in the designer generated file (Form1.Designer.vb).
I already correct my mistake. It's not in the designer generated file. It's in the base Form class that your Form1 class is inheriting from.
|
|
|
|
|
Maybe I'm missing something. You're trying to create your own Form class, removing the New constructor that doesn't take any parameters, and adding another New constructor that does take a parameter?? Am I correct?
You cannot remove the parameterless New method. Doing so will make the form unusable in the form designer since it will only create an instance of your form using the parameterless New method.
OK, what's the property you're trying to "force" on this form??
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
