I am running...
E:\CobolScript>e:\utils\cobolscript.exe
CobolScript Professional Edition - release 4.0 MS Windows
Copyright (c) 1996-2025 Matt Dean
Windows Pro x64
Windows 10 [Version 10.0.19045.5131]
I am not able to successfully execute the shm1.cbl program...
This is using VBScript, which can easily be translated to VB6
arrDateTime = Split("2023-07-06T14:34:21-04:00","T")
WScript.Echo arrDateTime(0)
WScript.Echo arrDateTime(1)
arrTime = Split(arrDateTime(1),"-")
WScript.Echo arrTime(0)
WScript.Echo FormatDateTime(arrTime(0), vbShortTime)...
For your reference;
VFP Advanced Version 10 - http://www.baiyujia.com/vfpadvanced/f_vfpa_about.asp
X Sharp - https://en.wikipedia.org/wiki/XSharp
Harbour - https://en.wikipedia.org/wiki/Harbour_(programming_language)
Joe
I am able to use 64-bit COM dlls from 32-bit, and 32-bit COM dlls from 64-bit.
I use a DLLSurrogate to accomplish this.
Ref: https://jpsoft.com/forums/threads/using-a-32-bit-in-process-com-server-dll-from-64-bit-tcc.9646/]Using a 32-bit In-Process COM Server DLL from 64-bit TCC[/url]
Joe
The author of the COBFD program is offering the PowerBASIC source code of COBFD to anyone who wants to upsize it to 32-bits.
https://forum.powerbasic.com/forum/user-to-user-discussions/programming/813074-32-bit-update-for-cobfd-bas?p=813076#post813076
He can be contacted via email (as noted in...
When JPSoftware removed the 32-bit version of Take Command Console, I could no longer use the 32-bit versions of In-Process COM DLLs that I had developed.
The workaround was to create a DLL surrogate, which allows me to use 32-bit versions of In-Process COM DLLs from 64-bit Take Command...
This is not a solution to your problem, but consider using the RunAsDate utility, instead of changing the date on your laptop.
From the website:
"RunAsDate is a small utility that allows you to run a program in the date and time that you specify. This utility doesn't change the current system...
I am developing a console application using VFP9.
At present, I do
ext = JUSTEXT(Sys(16))
...to determine the file extension of the complete application path.
When I am in the debugger, this returns FXP, thus (partial code)
If ext = "FXP" then
? theRecord
Else
.WriteLine( theRecord )...
I would like to update my Visual FoxPro 9 SP2 09.00.0000.5815 to 9.0.0.7423
Reference: https://support.microsoft.com/en-us/help/968409/fix-the-group-header-of-a-data-grouping-is-not-printed-at-the-top-of-a
9.0.0.7423 is a cumulative update.
Note that the link in the KB article no longer...
On my Windows 10 64-bit system, I have used;
vDosPlus
http://vdosplus.org/
vDos
http://vdos.proboards.com/
dbDos
https://dbdos.com/
You could also install DOS into a Virtual Machine.
Although no longer actively developed, I use vDosPlus to run my dBASE 5/Clipper 5.3/FoxPro DOS Applications...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.