Reputation: 298 Architect
- Active Posts:
- 1,754 (0.97 per day)
- 26-March 09
- Profile Views:
- Last Active:
- Yesterday, 04:42 PM
- OS Preference:
- Who Cares
- Favorite Browser:
- Favorite Processor:
- Favorite Gaming Platform:
- Your Car:
- Who Cares
- Dream Kudos:
- Expert In:
Posts I've Made
Posted 25 Feb 2014First off, a couple of advice points for you. Please, note, I'm having a go at you, just offering some friendly advice.
1. This is VB.Net code, so technically in the wrong forum. Don't create a duplicate topic as a mod will move it.
2. Have a look at using a naming convention for your variables, for example your variable TextBoxInput is defined as an integer, but reading the code, you can't tell that. My first thought was it was a textbox. If you use a standard naming convention whereby you prefix the variable with the datatype, it makes the code easier to follow. For example intTextBoxInput, would be more self explanatory. There are different conventions you can use, so chose one that works for you.
OK, in regards to the code. You will always drop into the Select statement regardless of whether you enter a valid number of not.
You could try putting your select case in "True" part of your if statement.
If ValidNumber then 'Select Statement Here Else 'InValid number message here EndIf
If there is another issue that you have, please post your updated code and advise where the error occurs.
Posted 19 Feb 2014My call was to limit the changes to those Microsoft have already done for VBA (as being an achievable objective).
I try and avoid the use of 3rd party controls (& Microsoft controls for that matter), though you can't always do this.
To be honest, my only major gripes about VB6 up to now are around the IDE, in that it seems to get flakier as the OS's move forward. Win7 had a form drawing issue (unless you reduce the colour scheme and a couple of other visual settings). On my Win8 laptop, the compiler will intermittently stop on lines indicating an issue, when you know for a fact there is no issue there (maybe my machine - I have nothing else to compare with). Probably haven't come across other needs as most of the tweaks are based on a similar theme and I guess you get used to working within the limitations. As said previously, anything new, I do try to write it in .Net (as much as a learning exercise for myself as anything).
QuoteWhat have you got against Venkys ? Don't you like poultry ? />/>
Let's just say it leaves a sour taste!
Posted 19 Feb 2014Thanks for reply
i want to create some tool but i do no how to write program in VBA6 will you help me
People here will be happy to try to assist, but you have to show some effort on your side.
VB6er has pointed you in the direction of the VBA reference and I'm sure by using Google you can find a number of references/examples by yourself.
Have a go at it...you may even surprise yourself and feel free to post back with any problems you're having along with any associated code (in [ CODE] tags), giving as much information related to the issue as you can, that way you will get more qualified answers to your questions.
Posted 19 Feb 2014I'm no expert in this area, but have a look at the connection string examples in the link below:
Looking at your code, your connection string doesn't appear correct for connecting to the DB file directly.
Posted 18 Feb 2014I've been reading this thread for a while and listening to both sides of the argument with interest.
I'm in the position whereby I work for a small company, which has a main core product written in VB6, but yet we also develop Mobile apps in C# (not sure why the decision was made to jump to C# and not VB.Net, but that' s a different story).
The scenario for ourselves and many other companies, is that they can't afford the investment to rewrite applications in a newer language and in some ways I can see the logic behind the reasoning. The application will still do the same thing as it does now.
Personally, I believe this to be a little bit false economy, as we, as developers using VB6, know we are on borrowed time. I'm also of the opinion that if you can't do something with a tool, you use a tool that gets the job done, you don't modify the tool to fit the job.
I've watched many iterations of the .Net framework pass by with many new features that would both benefit the applications and aid the development process, but unfortunately hands are tied due to financial constraints.
In regards to creating an updated VB6, where do you draw the line as to what features are added (or required)? 3rd party controls potentially won't work with the new system in "64 bit" mode, so there's scope for breaking things anyway.
I've been using VB since Version 3 (along with C and Assembler in previous jobs) and I feel I'm stuck in a rut with it. The tool does what we need in regards to supporting our core app, but I enjoy the time I get to work on our mobile apps in C# and where I would use VB to knock up concept apps in the past, I now use C#, as I find it just as quick to get things done. I'd love to have the time (and investment) to be able to rewrite our apps in .Net, but some companies just won't support it for one reason or another (or until they're forced to).
Not much of an argument for or against, just wanted to add my view on things.
- Member Title:
- D.I.C Lover
- 42 years old
- June 12, 1971
- Programming Languages:
- C#, VB
- Website URL: