How can I use my old VB6 customized SQLServer database application in Windows 7?
I can not upgrade my old VB6 EXE file.
VB6 Apps:
You can run 32-bit VB6 apps in windows 7.
The full scope of support is detailed here: http://msdn.microsoft.com/en-us/vstudio/ms788708.aspx
There is a thread here that covers some bits and bobs you may need to cover off: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/vb6-executable-will-not-run-in-win-7-64-bit/05c506d7-2ae9-4abd-91d6-9481b4b243e0
The main thing to realize is that you may have to manually install some of the pre-requisits you would have expected to be there by default on other windows versions.
SQL Server 7:
This may be more insteresting. You can certainly run a newer version of SQL Server and set the compatability level of your database as required - this may be sufficient.
I'd be surprise if you were able to install SQL Server 7 itself on Windows 7
I don't know about SQL Server 7, but VB6 will definitely run on Windows 7.
Related
I had SQL Server 2005 working when I upgraded to Windows 10. Now it won't work. I read that it is not compatible with Windows 8, according to Microsoft. Windows 10 is but the matured version of Windows 8, to me. Is there any way I can get SQL Server 2005 to work with Windows 10?
Have you tried to apply / re-apply SP4? I'm not saying it will work but it works in Windows 8. Not sure what you upgraded from.
This may help .. https://www.youtube.com/watch?v=cj859zcWhEM
uninstall inFlow before upgrading to Windows 10 and then re-install (because of compatibility issues with SQL Server 2005). This is pretty easy and can be done from the START menu by searching “Programs and Features” and once open, choosing to uninstall inFlow Inventory.
Not sure which version of SQL you’re using? You can check the version of SQL Server through the START menu by searching “Programs and Features.” In that window, look for “Microsoft SQL Server” and check the version (it will either be 2005 or 2008 R2). If you’re in 2008 R2 or 2012 you’re golden, no extra steps required).
So bottom line: if you’re planning to take advantage of the upgrade from Windows 7 to Windows 10 that’s great, but take a few minutes to double check your SQL Server version (as noted above) before you upgrade. Most of us won’t be affected but if you don’t, the upgrade could break inFlow and that’s no fun at all!
I'm having difficulty getting Arango 1.4.9 working on my Windows 2008 Standard (SP2) server. It's a fresh install. When I try to start Arango Server I receive this message:
The procedure entry point TryAcquireSRWLockExclusive could not be located in the dynamic link library KERNEL32.dll
I have tried both the 64bit and 32bit versions. I have run the installer as an administrator and vice versa. Any ideas?
TryAcquireSRWLockExclusive is from a newer Windows API. The Windows 2008r2 build uses newer Windows API features such as SRW (Slim/Reader Writer) API to improve performance. These are not available in Windows Server 2008.
I assume that you must recompile for Windows 2008 or ask for a suitable binary in the support forum (https://groups.google.com/forum/#!forum/arangodb).
Can i use dev c++ 4.9.9.2 on Windows Server 2008 R2, i mean that i tried using it on windows 8 but it didn't run. And we are restricted to use this IDE only from our university.
Server 2008 R2 is 64-bit OS.
According to their site, Dev C++ 4.9.9.2 only supports Windows 9x, NT, or 2000. Given that the Windows Server operating system series started in 2000 (with Windows Server 2000), and that Dev C++ 5 doesn't support it (even though it supports XP, a later released OS), I would surmise that it is not supported on Windows Server 2008 R2. However, you should be able to run it if you use Compatibility Mode.
You can use the following steps: (from How to Run Older Programs under Windows 8 -- For Dummies but copied down in case of link rot. This technique also works in Windows Vista/7/Server 2008 R2)
Right-click the program's icon and choose Properties.
When the Properties dialog box appears, click the Compatibility tab
and then click the Run Compatibility Troubleshooter button.
In its robotic way, Windows 8 tries to guess what version of Windows
your program needs, and then it applies the changes. If the program
begins working, you're through.
If the program still has trouble, though, move to Step 3.
In the Compatibility Mode section, select the Run This Program in
Compatibility Mode For check box and select the program's desired
Windows version from the drop-down list.
Check your program's box or look at its manual to see what version
of Windows it expects.
Click OK and then try running your program again to see whether it
works better.
If your older program doesn't run, it's time to upgrade to a newer version.
Disclaimer: Yes, I know Windows 8 is a pre-release and things won't necessarily work. I still need to do this.
I'm trying to install SQL Server Express 2008 R2 on Windows 8 32-bit (via Virtual Box). When I run the installer, I get an error:
Database installer returned error code -2147024893 (The system cannot find the path specified.)
The web installer didn't work either. WPI's log file tells me:
DownloadManager Information: 0 : Install exit code for product 'SQL Server Express 2008 R2' is -2068774911
I tried running this in compatibility mode for Windows 7. I can run the installer, click through the setup screen, and finally I get this error:
There was an error generating the XML document.
Error code: 0x84B10001.
How do I get this working, or, how do I debug/triage this? I looked through the logs, but I'm not too sure what they said; it might've been a registry-write error. Running in admin mode just causes the installer to not load, or a nice BSOD:
The answer, ironically, is quite simple -- I was installing 32-bit SQL Server on a 32-bit Windows 8. Instead, I moved to installing a 64-bit SQL Server on a 64-bit Windows 8.
Problem solved.
My company has a VB6 application using Crystal Reports 7 which a client has asked to be installed on Windows 7 32 bit. It is currently installed on Windows XP 32bit SP2 machines at the client. Connection to the DB is done via ODBC to SQL Server 2000 instance on another server.
On Windows 7, the installation works fine, however when you try to open the application, the error is given.
I have looked at the following:
Registering all the dll's and ocx files using regsvr32. Some will not register as they either are registered already or the following message is given "Make sure that "[name].dll" is valid DLL or OCX file and then try again." I read this forum thread regarding this: http://social.msdn.microsoft.com/forums/en-US/vblanguage/thread/0653f685-4526-45d9-89f3-8c479a6b4c62
Monitored the opening of the application using a ProcessMonitor application to try and spot if there is a missing dll or ocx file - this does not seem to be the case.
Reviewed the application according to this list and nothing seems to be against these guidelines
I've noticed two items in the knowledge base that relate to this
http://support.microsoft.com/kb/281848 - the comdlg32.ocx bundled with the application is version 6.0.81.69 and the one in the system32 folder on the dev machine (WinXP 32 bit) is 6.1.97.82. However if this was the issue then surely it would not work currently?
http://support.microsoft.com/kb/184898 - I'm not sure how to confirm that this is the issue
Finally, due to complexities, I am not allowed to make code changes to this application. Even if I was, I'm not a VB6 programmer, just the guy who got the terribly support project! If code changes are required, then I'll have to investigate using WinXP mode.
Update: I get the same error in XP Mode. That's a Win XP with SP3 VM. This runs on a Win XP SP2 VM, is there potentially something in SP3 that would have caused this to occur? Or is it just a fact of it being XP Mode?
I got the same error but I solved by using regsvr32.exe in C:\Windows\SysWOW64.
Because we use x64 system. So if your machine is also x64, the ocx/dll must registered also with regsvr32 x64 version
The file msrdo20.dll is missing from the installation.
According to the Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 and Windows 7 this file should be distributed with the application.
I'm not sure why it isn't, but my solution is to place the file somewhere on the machine, and register it using regsvr32 in the command line, eg:
regsvr32 c:\windows\system32\msrdo20.dll
In an ideal world you would package this up with the redistributable.
This download fixed my VB6 EXE and Access 2016 (using ACEDAO.DLL) run-time error 429. Took me 2 long days to get it resolved because there are so many causes of 429.
http://www.microsoft.com/en-ca/download/details.aspx?id=13255
QUOTE from link:
"This download will install a set of components that can be used to facilitate transfer of data between 2010 Microsoft Office System files and non-Microsoft Office applications"
You say it works once you install the VB6 IDE so the problem is likely to be that the components you are trying to use depend on the VB6 runtime being installed.
The VB6 runtime isn't installed on Windows by default.
Installing the IDE is one way to get the runtime. For non-developer machines, a "redistributable" installer package from Microsoft should be used instead.
Here is one VB6 runtime installer from Microsoft. I'm not sure if it will be the right version for your components:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7b9ba261-7a9c-43e7-9117-f673077ffb3c