I've looked to see if this has been asked before, but only see questions relating to VB6 installations, not .exe files MADE FROM VB6. Apologies if this has been asked and answered.
I have some tools I built with VB6 and our team has been using them successfully for some time now. However, we are migrating to Windows 7 and it seems there are now issues with using the "Microsoft ODBC for Oracle" driver.
I can write in VB.Net, but I don't yet have it and don't know when I'll get it.
Any advice? Time is of the essence here, and a big thanks to all who answer.
Related
I've some .vbp,.frm files and i want to open them with VB 6.0 but i am using Windows 8.1 is there any version of Visual Basic that is compatible with Windows 8.1.Please do suggest me.Thanks in Advance.
Whats not working? Microsoft is supporting run time files for at least a few more years works up to 10 and maybe will be for a few more versions, install vb 6 and it should have no problem running unless the systems messed up.
As indicated by others, the VB6 development tools can be installed and work (with limitations) on all versions of Windows Longhorn (including Windows Vista, Windows 7, Windows 8, Windows 8.1, on up through Windows 10). Most of the limitations are project types rendered useless when Microsoft ripped away the infrastructure for them as they mutated IE and IIS over the years with little regard.
So without a license for VB6 or preferably VS6 there isn't much you can do with these files. If the projects are fairly simple you might get somewhere trying to make the completely unsupported VB5 work if you have a license for that, or if the project files are for even simpler applications VB5CCE might be of some limited use if you have that.
But in general there are no other products that can use these files to any useful extent. So as already covered many times in other questions here and elsewhere you need VB6/VS6 and the only remaining source is an MSDN Subscription or used or remaindered copies that may be for sale here and there.
This question already has an answer here:
ODBC connection to Access database in 64-bit Windows
(1 answer)
Closed 8 years ago.
I need to create a datasource for Microstation V7 in Windows 7(64bit), but I can't find "Driver do Microsoft Access (.mdb)" ODBC driver.I looked in Control Panel>Administrative Tools>Datasources(ODBC) and when I click the "add" button in the User DSN I only see "SQL Server" and "SQL Native Server". Where is Driver do Microsoft Access (.mdb) or how can I install it?
This is most likely a 32/64 bit problem.
I assume Microstation is a 64-bit program and Office are 32-bit applications. This mismatch is hard to overcome.
Maybe this answers your question.
I'm currently using VS2008 with SQL Server Express 2005 with great success. I got all the bits to install VS2010 and SQL Server 2008 Express R2, and plan to tackle this over a weekend. My question is this:
What is the best approach to update my system to the latest bits. I'd like to uninstall VS2008 and SQL Server 2005 completely and just use the latest technologies. However, I don't want all the leftover fluff after install and would like to be able to know that things are going to go as planned (although they seldom do). Ultimately I want a clean configuration to get up to date with the latest and greatest stuff.
Could anybody see a problem with this process:
Uninstall SQL Server 2005
Uninstall VS2008
Install VS2010
Install SQL Server 2008 R2
I've searched all over the internet for tips on how to approach this. Most everything that I'm finding are the problems that people have when doing this. However, that's typically what the internet is for; when you have problems. So I'm reading everything with that in mind. :) I was going to "just do it", but figured it might be best to post the question out here to see if anybody has suggestions or tips for this process.
I'd appreciate any comments. Of course, I'll update this post once I've completed the steps so future geeks can benefit from my findings (good || bad).
You can just save yourself some time and install VS2010 and SQL2008 side by side with the current versions you have - they co-exist nicely.
I'm answering my own question because nobody else did... Perhaps this was a poorly formatted question.
Regardless, I followed the steps outlined in my initial question and had a few nuances along the way.
After upgrading my ASP.NET MVC application to .NET 4.0 Framework doesn't allow me to debug anymore.
I had to jump through hoops to reference `System.Core` in order to allow my Linq queries to work again.
Cannot manage SQL Server Express 2008 R2 databases from 2008 Management Studio; it only lets me manage old SDF files.
Had to Reinstall JetBrains Resharper (not a big deal, but a nuance none-the-less).
Other than that, I'm very pleased with how easy the process was. I still need to figure our the ASP.NET debugging issue, and plan to update this answer once I do...
How can I create a setup file in visual basic 6 after completion of my programming work?
Front End language is Visual Basic 6,
Backend : MS Access 2003 and
Report Tools : Crystal Report 8.5. Operating System Windows XP.
You need to be a little clearer about some of this.
"Front end/back end" is really terminology and a thought pattern from the MS Access world. It doesn't really apply to VB6 development in any meaningful way unless you're doing something really odd like automating instances of MS Access.
That's about the only place where any "MS Access runtime" comes in as well. If you're actually using Access Reporting you might be doing this though - which seems odd but anything is possible.
See Deploying Complex Microsoft Office Access Runtime-Based Solutions.
Much more likely what you are trying to say is that you have a VB6 program that is using a Jet MDB as an embedded database, and using Crystal Reports 8.5 for reporting.
There should be no issue about any "runtime" for Jet on Windows XP, since Jet 4.0 is shipped as part of the OS even as far back as XP RTM (gold). It is also extremely unlikely that XP will have an MDAC release any older than 2.7 (see Microsoft Data Access Components (MDAC) release history).
So this leaves you looking for a way to package your VB6 program, any immediate dependencies such as possibly the VB6 runtime components, and the Crystal Reports 8.5 runtime components. You may also have INI files, etc. to bundle in there.
A long, long time ago (1998?) the PDWizard was replaced for most purposes by Visual Studio 6.0 Installer 1.0, and shortly after VSI 1.1 was released (1999?) which made up for a number of ills. This is a pretty basic tool for authoring Windows Installer packages, but it should meet your needs.
Along with this you'll want the recent merge modules for your dependencies: Merge Modules for Service Pack 6 for Visual Basic 6.0 and Visual C++ 6.0.
Then of course you need a merge module for Crystal Reports 8.5, and for this we have to turn to the community because BO didn't start releasing them until CR9. One place to look for this is InstallSite: Seagate Crystal Reports 8. Your real problem is that CR8.5 is ancient.
If this doesn't work out for you, you can always hope that CR8.5 Dev installed on your machine with a "good enough" set of .DEP files (which tell setup authoring tools what subdependencies each dependency has, among other things). This may still let you use VSI 1.1 to succesfully package your application with CR8.5.
You might also look at for-pay packaging tools as already suggested. If desperate enough you might look at some legacy installer technologies too, just in case their communities have addressed your issues.
If I misunderstood and you really do use your VB6 program to automate an instance of the "MS Access 2003 Runtime" you'll probably have to build some hybrid package.
But normal VB programs do not use Access or Access Runtimes to open and work with Jet databases.
You can search google for package and deployment vb6
and you will find millions of links showing in steps how to do that.
The Package & Deployment Wizard is quite primitive and not well-suited to distributing things like the MS Access runtime and Crystal Reports. You'd be better off using one of the more powerful commercial products like InstallShield or Setup Factory. However, these can be pricey (especially InstallShield).
There are also free products like Inno Setup and Nullsoft, but these may not be as easy to use or may lack some important features.
Bob's suggestion of using Visual Studio Installer 1.1 for a Visual Basic 6 application is sound but the Microsoft link he has given for the download does not work. I guess MS thinks nobody needs VB6 anymore. After searching a little I found a 2008 snapshot of MSDN page in web.archive.org complete with setup files:
http://web.archive.org/web/20080513102621/http://msdn.microsoft.com/en-us/vstudio/aa718352.aspx
Good suggestions above.
While it might seem unlikely that VB6 app could possibly be in use, there are those of us in the public sector that keep VB6-like apps and even Access apps alive because public dollars are not in a hurry to replace app that still work. A frequent mantra heard in many places is that you leave it alone if it is not broken. Broken enough that is--otherwise baling wire works just fine as long as VB/VBA developers can still found.
I want to trial Windows 7 but wondered if anyone who has done so already ran into any issues specifically related to development?
i.e. problems with VS2008, SQL Management Studio and SQL Server, MySQL, PHP etc. etc.
Examples from XP -> Vista: in Vista there was a sudden loss of an SMTP server. And there were initially (if I remember correctly) issues with VS2005 with I seem to remember a patch coming out later to remedy.
EDIT: or on the contrary any big advantages or benefits to developing on Windows 7!
I been using windows 7 for a while now.
I been using VS2008, netbeans, tomcat, sql manager studio, mysql etc...
And i actually find it more stable and faster then windows vista.
There aren't many advantages to developing on Windows 7 before it's released. Most development features are a function of the IDE, not the OS. So, you might want to consider instead if you should be developing on Visual Studio 2010 instead of VS2008. Instead, you're more likely to have compatibility issues, although for the most part, Windows 7 is much more compatible with existing software than Vista was when it was in beta.
There could be one advantage to developing for Windows 7 before it's released -- you have a head start in taking advantage of features that competitors haven't yet, giving you an advantage in the market. That's the theory at least. That assumes you're going to develop something that uses a feature only available in Windows 7. That assumes you wouldn't be better off with the larger number of sales you'd get by developing something that works on existing platforms.
The only issue I've encountered so far involves compiling older vanilla C programs with Visual C++. You're usually presented with an error like so:
mt.exe : general error c101008d:
Failed to write the updated manifest
to the resource of file
".\Release\SomeProgram.exe". The
binary is not a valid Windows image.
You have to add an empty resource file to the solution.
More on the issue here.
I've never gotten any of the new audio stack examples working; thus this question. API works, documentation is... a bit lacking at the moment; sure to be fixed by RTM.
Other than that, Windows 7 has been faster than and just as stable as Vista (2 crashes from RTM, 0 crashes after SP1) was for me. Truly, you should be developing on Vista and testing on Windows 7 RC as a general practice with respect to pre-release operating systems; but I think we'll get away with it just fine in this particular case.
My advice would be to not develop on Windows 7. Note that I don't mean you shouldn't target it as a platform, just that you should be doing your development on a stable platform.
I personally won't trust a new release of Windows (or Linux for that matter) until it's been in the wild as a proper product (not release candidate) for many months. For Windows, I tend to wait until the first real service pack plus a month for all the nigglies to be fixed.
For Linux, I'm still using Ubuntu 8.04 LTS, not 8.1, and certainly not the 9 alphas.
Test machines are another matter, you should always have one at the "latest and greatest" level for testing, but I consider the development machine of prime importance, needing a stable platform.
No problems from my end yet, been working on a c# app with visual studio 2008 x64, and php web apps with dreamweaver cs3 and netbeans.
Windows7 seems to be just vista with more bells and wistles and a bit more responsive, not to sure if to much really change "under the hood" so to speak. But I have nothing to back that statement up with...
I've been using Win7 for a couple of months now and never had a problem. I went straight from XP to 7 and the only problems I faced were related to configuring SourceGear Vault to work with IIS7...other than that,it's been all good.
I use VS 2005, VS 2008, SQL Server 2005, Infragistics NetAdvantage, and a couple of third party components.
Although I haven't seen any advantages for the development side of the applications, I'd recommend you to upgrade to Win7 only for the better feel of a complete OS. I mean XP was good, but I really dig Win7.