|
I say yes that VB6 is old.
I completely understand why anyone would want to perpetuate it.
There is a big huge learning process to move to a completely different language.
Most programmers have huge numbers of applications currently in use that need maintenance.
There is not much that “can’t be done “ with VB6
Finally, I have a mantra that I have very painfully learned years ago:
“IF IT AINT BROKE, DONT FIX IT”
|
|
|
|
|
Quote: IF (YOU THINK) IT AINT BROKE, DONT FIX IT
Fixed that for ya. 
|
|
|
|
|
|
David Lema son wrote: Ddddd
But what is the question? Also, you are on the VB forum and your subject is C# (there is a separate forum for that). C# is one semitone short for discussions on D.
The best help that I can think of based on your text is ... (Using MS Windows Calculator in Programmer Mode)
Hex: Ddddd
Dec: 908765
Oct: 3356735
Bin: 11011101110111011101
|
|
|
|
|
jsc42 wrote: But what is the question?
Look at his member profile: Member since Thu 19 Jan 2023. SPAM.
Graeme
"I fear not the man who has practiced ten thousand kicks one time, but I fear the man that has practiced one kick ten thousand times!" - Bruce Lee
|
|
|
|
|
I already reported his message as "inappropriate"
|
|
|
|
|
Hello,
We can use API to communicate two different applications.
I have one major doubt, that I am having my VB6.0 application need to integrate with third party webbased application.
Is this possible to use API keys through vb6.0 code to link with third party API?
Thanks
|
|
|
|
|
This has nothing to do with the language being used. Yes, you can use the API keys, but it's your code and/or library that communicates with the API that's going to use the keys.
But, WHY ON EARTH ARE YOU USING VB6? It's been dead for 20 years now. New development in VB6 is a complete waste of time. You're going to end up rewriting this app sooner than you think. VB6 runtime support will end with the end of support for Windows 11. Support for the 22H2 version of Windows 11 will end in October 2025, just under 3 years from now.
|
|
|
|
|
Thanks for the reply.
Actually main reason behind using vb6 is we have developed one big application in vb6 before 12 years which is currently been used very much finely and perfectly.
And it will be a big taks for us to upgrade it to vb.net hence instead of upgrading we are still using it.
Now just small changes are there which is like to integrate web based applications data with that application.
|
|
|
|
|
I suggest you start planning the change to another platform, you have 3 years!
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
OK, but you have a lot of planning to do. You WILL be re-writing this thing. Are you going to wait until it's too late to do it?
You better start now.
|
|
|
|
|
Don't worry too much about people telling you that VB6 is outdated, dead, or both. There are millions and millions and millions lines of VB6 code out there, keeping companies running and being profitable. And if you have VB6 skills, you definitely have employment and earnings opportunities for many years to come. I should know: I am quickly approaching my 70th birthday, I am retired, and still bring home quite a bit of bacon by free-lancing, carefully selecting what I want from a ridiculous number of offers/requests.
Oh... when someone tells you that VB6 is outdated, dead, or both... just remind them of COBOL... 
And to come back to your question: yes, VB6 can be used to interact with many API. Depending on the API, you will use different tools and/or techniques. Sometimes it will be more difficult than using other, more modern languages. In other cases, strangely, it will be easier. Go figure.
Good luck with your project!
|
|
|
|
|
 This just goes to prove the point that VB6 applications should be retired and rewritten into a more modern language. You have a limited future as a viable developer and you are able to be very picky about which jobs you take on. While there may be millions of productive lines of code out there finding a young developer to support it is a challenge.
Encouraging anyone to continue with VB6 is doing them a disservice.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
Thanks a lot.
gvidali thank you very much..such a relief from this tension.
Now i am going to search API key and definitely link with my VB6 application..
|
|
|
|
|
It is interesting that you ignore the advice of two respected members with high reputations, but accept it from someone who has hardly contributed anything to these forums.
|
|
|
|
|
No no ..
Even I am thankful to all of you for the reply and solutions.
I will think on evryone's opinion surely.
Thats why i have started working on it also.
But for API key, i need to integrate it in my existsing system thats why i said i am relieved from the tenion thats all.
|
|
|
|
|
Here you go:
https://stackoverflow.com/questions/122607/how-to-consume-a-web-service-from-vb6
The useful life of a "typical" program is 5 years; obviously, you (and I) don't believe in typical.
(I'm not one of the respected ones).
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
|
Hello good people. Please I'm using Vb.net 2019 and I have a setup project in the solution explorer which I have packaged and installed on other machines and it works fine.
About some fews weeks later, I realised the setup project was mysteriously unavailable and I tried to repackage using Add new Project. In the add a new Project window, I searched for setup in the template but nothing was found. I came to the main project and clicked on Extensions and found that Microsoft Visual Studio Installer Projects was still installed and ticked. I'm stuck and don't know what to do now. Please I need your urgent help. Thanks
modified 19-Dec-22 3:49am.
|
|
|
|
|
|
Sorry, wanted to type 2019 pls. Thanks for the correction.
|
|
|
|
|
Option Explicit On
Imports Excel = Microsoft.Office.Interop.Excel
Public Class Form1
Private Sub Button1_Click(sender As Object, e As EventArgs) Handles Button1.Click
Dim xlApp As Application
Dim xlWorkBook As Excel.WorkBook
Dim xlSheet As Excel.WorkSheet
xlApp = CreateObject("Application Excel")
xlWorkBook = xlApp.xlWorkSheets
xlSheet = xlWorkBook.Sheets("Données principales")
xlSheet.activate
MsgBox("h")
MsgBox(xlSheet.Range("A1").value)
End Sub
End Class
|
|
|
|
|
... and where did you have addressed the workbook itself ?
|
|
|
|
|
And is there supposed to be question there?
|
|
|
|
|
My guess (based on the subject text) is that your question is "Why do I have to put 'Excel =' in the 'Imports Excel = Microsoft.Office.Interop.Excel' line when I could just do 'Imports Microsoft.Office.Interop.Excel'?". If that is your question, the answer is that the 'Excel =' provides a shorter name than having to write the whole lot every time, so rather than having to type
Dim xlWorkBook As Microsoft.Office.Interop.Excel.WorkBook you can simply type
Dim xlWorkBook As Excel.WorkBook . If that is not what your question is, then what is the question?
We at CP are good at answering questions; we are not quite as good at trying to guess what the question is 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
