We're in the process of converting our two FoxPro systems to new technology, but meanwhile we need to upgrade our server and I am trying to find out whether our legacy systems will run there. We'd prefer to go to Windows Server 2019, but using Server 2012 is possible. Our stations are Win 7 or 10 Pro, some 64-bit.
One system is in Visual FoxPro 9 and uses its native DBFs and some DBFs in FPD 2.6 format. Certain graphical and document functions (e.g.: OCR) are performed by calls to LeadTools 12.0. The application also calls Outlook.
The second system is a single-user application in FoxPro for DOS 2.6 run from an .app file. The 32-bit stations run this natively, while the 64-bit stations use the product, vDOS, to allow the 16-bit FPD to run there. The application wants to reside on the server since multiple stations can run it, albeit at different times.
Any help is much appreciated. Thank you!
Will a Visual FoxPro 9 EXE run on those server operating systems? Yes.
Will a Foxpro For DOS or FoxPro for Windows EXE run on those server operating systems? No. Those flavours of FoxPro are 16-bit, and as such would require a 32-bit version of Windows Server, the last of which was Server 2008.
However I suspect you are not running either of these on the server. You have a shared folder on the server with the DBFs in it, and the executables are running on workstations.
So if you have a 64-bit OS on the workstation then you can only run the Visual FoxPro exectuable directly. If you had a 32-bit OS on the workstation, you can run both Visual FoxPro and FoxPro for DOS\Windows executables.
Your question is really 'can I put the DBFs in a shared folder on those server operating systems and access them from client workstations?', and yes you can.
Related
How could I read an Excel file with SSDT-Visual Studio 2019 under Windows Server 2016 64-bit ?
I see there are a lot of blogs describing similar issue but I'm still not able to solve my problem.
I would like to read an Excel file within my Visual Studio 2019 (SSDT Toolbox) under our Windows Server 2016 64-bit.
At first attempt (during the development) I got this error message "The requested OLE DB provider Microsoft.ACE.OLEDB.16.0 is not registered. If the 32-bit driver is not installed, run the package in 64-bit mode."
Ok, I understand VS 2019 is a 32-bit app so it, by default, tries to use 32-bit driver.
Through multiple tests I tried the actions below but none of them have solved the issue :
set the Run64BitRunTime as True
set the "Processor Architecture for AnyCPU Projects" as x64
It seems modifying those settings would apply only at RunTime level i.e at the compiled version of the package, not during the development.
When I use SQL Server Import and Export Data Wizard 64-bit (and save the SSIS Package) it do works BUT it does not help reaching 100% of my goal. The reason I use SSIS is to do complex ETL , not only reading an Excel file. Reading such file is only a small part of the process (otherwise SSIS would be quite underutilized)
The biggest constraints I currently have are:
As per company restrictions, we could not install 32-bit driver on that machine
I know Visual Studio 2022 would be 64-bit but unfortunately, at this time (October 2022), it does not have SSIS module yet
Could anyone help me to solve this?
Any helps or tips would be appreciated.
My environment:
Windows Server 2016 64-bit
SQL Server 2019 with SSIS module installed
Visual Studio 2019 with SSDT module installed
I need to install Microsoft XML Parser 4.0 from Inno Setup.
How can that be done?
I was given a task to embed MSXML in the installer of ours. It's a proprietary piece of software our company makes (for accounting, it uses XML to store and exchange data). Apart from modern systems It's also going to be installed on many old systems using Windows XP.
I'm using Inno Setup 6.1.2.
Also, is there a quiet mode of installation as an option? So the users won't have to click anything and just be notified that MSXML was installed?
Did you Google this?
https://silent-install.net/software/microsoft/msxml_parser/4.30.2107.0
Eg:
msxml.msi /qn /L* "%temp%\XML Parser 4.30.2107.0.log" /norestart ALLUSERS=2
If you look at the Msiexec (command-line options) it does say the qn switch will display no user interface.
Somewhat of an aside, the requirement of installing both on XP and on 'modern' systems may create a conflict that you or your installer will have to resolve.
From Installing and Redistributing MSXML 4.0:
System Requirements
MSXML 4.0 is supported in Windows Server 2008 R2, Windows 7, Windows
Server 2008, Windows Vista Windows Server 2003, Windows XP, and
Windows 2000
From Installing and Redistributing MSXML 6.0:
System Requirements
MSXML 6.0 is supported in Windows Vista; Windows 2000 Service Pack 4;
Windows Server 2003; Windows Server 2003 Service Pack 1; Windows XP
Service Pack 1; Windows XP Service Pack 2.
MSXML 6.0 is preinstalled with Windows Vista. For earlier versions of
Windows, you can install MSXML 6.0 as a separate download.
So you can only use MSXML4 below Vista. And with Vista and above you should be able to reply on MSXML6 already existing.
Your installer could perform an OS version check (alt ref) and then only install MSXML4 if needed. Or you might be able to detect specifically if MSXML6 is installed and then install MSXML4 only if not (assuming therefore its an older system).
But I would test your application (if you haven't already) and see if it will run against MSXML6; it may, without changes. If so then I would forget MSXML4 and include MSXML6 in the installer instead (*). That way your installer could just run it 100% of the time, and expect that on Vista and up it would just do nothing. Your installer would therefore be simpler plus you would be taking advantage of "MSXML 6.0 provides security and performance improvements over earlier MSXML versions." noted here.
(*) Unless you have to run on WinXP pre-SP1?
I have fairly large legacy (read only) VSS 8 database that is currently sitting on a windows 2003 server.
As part of an infrastructure consolidation I am being asked to move it onto a new Windows 2012 server. I can't find any notes on whether or not VSS8 will run on 2012; before I even attempt this do you know of any issues running VSS on Windows 2012?
Is it easier to flip the old server to a VM and keep it for posterity and those rare occasions we want to know what someone did in the naughties?
The database itself is merely a fileshare, so you don't have to install the accelerator if you don't want to/are unable to.
In the weeks since asking have deploying VSS2005 (with the runtime available on the server) onto Windows 2012 enterprise. The applications install with a warning about versions but they run fine; including the admin tools for users and checking the consistency of the databases. The end user side all works well too.
Zorin is a version of Linux which is very Windows-like. I am looking at their home page:
http://zorin-os.com/
and it says:
Zorin OS gives users more flexibility. It allows you to use Zorin OS
alongside your current operating system and run Microsoft Windows
programs in Zorin OS with the help of WINE and PlayOnLinux.
Does this mean I could use Visual Studio 2012 on Linux?!?!
Ok, so Wine is a compatibility layer which allows you to execute windows executables on your linux system. PoL is just a graphical frontend with some others functionalities.
You can use it on any linux system, it's not exclusive to Zorin.
However, executing windows applications through wine isn't always successful, especially with huge projects as Visual Studio which is using tons of native windows functionalities.
And indeed, when we check the reports, VS2012 doesn't work at all.
You can always try to install it, but when even the installer doesn't launch... You know there is no luck.
Possible or not?
I know Sharepoint 2010 Server won't even run on a client side of Vista/Windows 7 64-bit, forget about Windows XP 32-bit.
But if I can install and use Visual Studio 2010 on Windows XP just fine, shouldn't Sharepoint development tools also work on Windows XP 32-bit?
The thing is I have a very old laptop (from 2005) that doesn't even support 64-bit architecture so I am stuck with WinXP 32bit.
If there is any way at all of (Remote?) Sharepoint development on Windows XP 32-bit with VS2010 please let me know.
Most of what the developer tools offer you make two assumptions:
You are running on a 64-bit architecture
SharePoint is installed side-by-side with Visual Studio
Running on a 32-bit XP machine breaks these assumptions. Many of the built-in Visual Studio productivity aids, such as the deploy and retract commands, will fail. I couldn't even create a project using the SharePoint 2010 project template under similar conditions.
You might make some headway by using regular class library or web application projects, copying SharePoint .dll's from a server's GAC (for use as references) and by manually creating your .ddl and .wsp files using MakeCab (as I did with 2007, with a little help from PowerShell); however, it sounds excruciating compared to running on Vista SP2 X64 or Windows 7 X64 with SharePoint installed.
As per the above answer, VS 2010 SharePoint projects require a local installation of SharePoint. You can use external tools for doing your development, such as WSPBuilder, but I do not recommend this approach. You are best sticking to the MS tools.
Your options are:
Upgrade to Windows 7 x64 or Server 2008 R2
Run VMWare Server (free) which should enable you to run a 64-bit VM on a 32-bit host (I think? Not sure about this assumption actually), and create a VM with Win7 x64 or Win 2008 R2 for SP development.
You can use Win7 64bit as your dev environment
http://msdn.microsoft.com/en-us/library/ee554869.aspx